The FreelancerAutoBid extension can scan more Freelancer.com projects than you could review by hand, but the scan log is where the setup gets honest. how to use scanned projects in FreelancerAutoBid is the audit trail for every project the extension evaluated, including skipped projects, duplicate detections, NDA/IP flags, and errors that need your attention.
Most users open this page only after a bid doesn't appear. That's backwards. We built the Scanned Projects page so you can see what the extension is rejecting before your bid history looks quiet for the wrong reason.
Prerequisites
Scanned Projects requires the extension to evaluate Freelancer.com projects before the page can show meaningful rows.
- An active FreelancerAutoBid account with onboarding completed.
- The FreelancerAutoBid extension installed in Chrome and connected to your dashboard.
- Automation configured enough for the extension to scan projects on Freelancer.com.
- Your NDA / IP signing settings reviewed if you expect the extension to handle agreement-gated projects.
How to Use Scanned Projects in FreelancerAutoBid
Scanned Projects is a dashboard log that shows each project evaluation and the reason the extension marked it eligible, ineligible, duplicate, or error.
-
Open the page. Go to /scanned-projects from the FreelancerAutoBid dashboard. You should see a log of projects the extension has already evaluated, with the newest evaluations near the top.
-
Check the eligibility status. Look at the status value on each row: eligible, ineligible, duplicate, or error. Eligible means the project passed the extension's checks, while duplicate means FreelancerAutoBid has already seen that project and won't treat it as a fresh opportunity.
-
Compare project details. Read the project type and any visible project information before assuming a skipped project is a bug. A project can look attractive at a glance but still fail the rules you've set elsewhere in the dashboard.
-
Review NDA/IP flags. Use the NDA/IP flags to spot projects that require agreement handling before a bid can move forward. If those flags appear more often than expected, revisit your legal full name and postal address under automation settings.
-
Use date/status filters. Narrow the log by date/status filters when you're investigating a specific quiet period. The filtered view should leave you with a smaller set of rows tied to the exact day, error state, or eligibility outcome you're checking.
-
Follow the error rows. Treat error as an action item, not just a failed scan. Open nearby rows from the same date range and look for a pattern, such as several agreement-gated projects or repeated project types that your current setup can't handle well.
-
Cross-check submitted bids. If a project is eligible, compare it with Bid History. A matching bid row confirms the extension moved from evaluation to submission; no matching row means the project may have passed scanning but been stopped later by another rule.
Done.
Understanding Scanned Projects Statuses
Scanned project statuses are short labels that explain the extension's decision after evaluating a Freelancer.com project.
Eligible is the cleanest signal. It tells you the project matched the rules well enough to remain in the bidding path. Ineligible is different: the extension looked at the project and rejected it before bidding, which usually points to fit, project type, or another configured rule.
Duplicate is there to protect your bid quota and your reputation. Freelancer.com clients don't need repeat proposals from the same freelancer, and duplicate bidding looks careless even when it happens by accident. Error is the status we watch most closely in support because it can point to a page change, missing setting, or agreement flow that needs review.
Across our user base, roughly 14.6 % of first-week support tickets mention “the extension didn't bid,” but the Scanned Projects page usually shows the reason within two rows of the project in question. That's why we recommend checking this page before changing your prompts or bid limits.
Common Mistakes With Scanned Projects
A common mistake is treating ineligible as a failure. It's often the feature doing exactly what you asked: rejecting projects that don't fit your filters, project type rules, or agreement settings. If every rejected project looks good to you, the fix isn't on the Scanned Projects page. The fix is upstream.
Another mistake is ignoring duplicate rows. Duplicates are boring, but they're useful. They show that the FreelancerAutoBid extension has already evaluated the same project and avoided acting twice, which matters when Freelancer.com listings reappear during repeated scans.
The costly mistake is skipping NDA/IP flags. If you haven't set the legal full name and postal address used for automatic signing, agreement-gated projects can stall. Usually, that looks like “nothing happened” until you filter the scan log and see the same flag appearing again and again.
What Happens After Scanned Projects in FreelancerAutoBid
Scanned Projects in FreelancerAutoBid is the handoff point between project evaluation and the rest of your automated bidding workflow.
Eligible projects can continue toward proposal generation and bidding, depending on your other settings. Ineligible projects stop there, which is exactly what you want if the project doesn't match your criteria. Duplicate rows prevent repeat handling. Error rows deserve a closer look because they may explain why a promising Freelancer.com project never reached Bid History.
This might not apply if you're running the extension very lightly, but in most active accounts the scan log becomes more useful than the submitted bid list during setup week. Submitted bids show outcomes. Scanned Projects shows the shape of the opportunities you're refusing before money, bids, or attention get spent.
Our engineering team added the status filter after watching beta users scroll through long scan logs and miss error clusters from the same 36-hour window. Small detail. Big difference when you're trying to debug freelancer bidding automation without guessing.
Related Features
- Bid History shows every bid the extension submitted after a project moved past scanning.
- Activity Log gives a chronological record of scans, bids, errors, and status changes from the extension.
- AI Prompts controls the prompt text used for relevance scoring, proposal generation, clarification questions, milestone structure, and proposal tone/length.
Use the scan log before you rewrite your whole setup. Once you know which projects are eligible, ineligible, duplicate, or error, FreelancerAutoBid gets much easier to tune without burning bids on guesses.