Contractor pages get crawled but never indexed when Google fetches them and decides they add too little that is unique, or when it finds the URLs and never gets around to fetching them. The fix starts with the Page indexing report in Search Console: identify which status you have, decide whether the page deserves to be indexed, then correct duplication, thin content, weak internal links, or slow hosting.
Key Takeaways
- “Crawled – currently not indexed” means Google fetched the page and has not added it yet.
- “Discovered – currently not indexed” means Google knows the URL but has not crawled it.
- Near-identical city pages and thin project pages are the most common contractor triggers.
- Weak internal links, bloated sitemaps, and slow hosting often explain pages that are only discovered.
- Request Indexing does not guarantee inclusion, and each property has daily limits.
- Some pages should stay out of the index on purpose, so audit before you fix.

What Crawled and Discovered Actually Mean
Many contractors open Search Console and find a long list of pages marked not indexed. These labels are not penalties. According to Google’s Page indexing report documentation, “Crawled – currently not indexed” means Google fetched the page but has not added it to its index, and it may be indexed later. “Discovered – currently not indexed” means Google knows the URL exists but has not crawled it, often because Google expected the crawl to overload the site.
The two statuses point to different problems. A crawled page is a value problem, because Google looked and was not convinced. A discovered page is a priority or capacity problem, because Google has not looked at all. Treating them the same wastes time. Indexing is only one slice of technical SEO for contractors, but it decides whether anything else gets a chance.
The same report lists other reasons a page may be left out, including noindex tags, robots.txt blocks, soft 404s, and duplicates where Google chose a different canonical. Those are easier to verify, because they trace back to settings on your own site. In Search Console, each reason sits under Indexing, then Pages, with a sample list of the affected URLs.
Why Google Crawls a Contractor Page and Still Skips It
When Google has fetched a page and left it out, the page usually looks redundant or thin. For contractors the pattern is familiar. One service page is copied for twenty towns with only the place name changed. Project pages carry a title, six photos, and two sentences. Archive pages repeat snippets of posts that already exist elsewhere. A page can also be thin without being short. A long page that restates the same generic advice every other site publishes gives Google little reason to keep it. Google does not promise to index every page it crawls, and pages that add nothing distinct are easy to skip.
Duplication also comes from technical settings. When several URLs show the same content, Google picks a canonical version and may leave the rest out. Fixing it takes practical contractor canonical tags plus genuinely different local content, because a canonical tag alone will not give a thin page a reason to exist.
Consider a hypothetical remodeler with kitchen remodeling pages for 25 towns. If most say the same things with different place names, Search Console may list many of them as crawled but not indexed. Consolidating them into a few strong regional pages, each with real projects, local permit notes, and photos from that area, gives Google something distinct to index.
Why Google Finds Pages and Never Fetches Them
A discovered status often means the page sends weak signals of importance. Pages buried five clicks deep, orphan pages with no internal links, and URLs that appear only in a sitemap give Google little reason to prioritize them. Link new pages from the main navigation, from the parent service page, and from related posts so the path to them is obvious.
Capacity matters as well. Google ties this status to crawls it expects might overload a site, so cheap or overloaded hosting that responds slowly or throws intermittent errors can hold back crawling of the whole domain. Bloated sitemaps full of redirects, error pages, or non-indexable URLs waste attention too, as do filter and search URLs that create endless variations. Keep the sitemap to live pages you actually want indexed.
A brand-new site, or a freshly published batch of pages, may also just need time. Waiting a few weeks and watching the trend is usually wiser than reworking pages that Google has not had a fair chance to evaluate. If the status holds for months while other pages are indexed, treat it as a priority problem and strengthen the links and structure around those URLs.
Match the Status to the Likely Cause
Search Console groups pages by reason, which gives you a head start. The table maps the most common reasons on contractor sites to a sensible first fix.
| Search Console Status | What It Means | Common Contractor Cause | First Fix |
| Discovered – currently not indexed | Google knows the URL but has not crawled it | Weak internal links, slow hosting, bloated sitemap | Link the page from related pages and trim the sitemap |
| Crawled – currently not indexed | Google fetched the page but has not indexed it | Near-identical city pages, thin project pages | Add unique detail or merge similar pages |
| Excluded by noindex tag | A noindex directive blocks indexing | Staging setting left on after a redesign | Remove the tag, then retest the URL |
| Blocked by robots.txt | A rule stops Google from crawling the page | A plugin or developer rule covering a whole folder | Edit the rule, then retest |
| Duplicate, Google chose a different canonical | Google prefers another URL for the same content | Service pages copied across towns | Differentiate the content and review canonicals |
| Soft 404 | The page reads as not found but returns success | Empty galleries or removed project pages | Restore content or return a true 404 |
Noindex tags and robots.txt rules are settings you control, which makes them the quickest to check. Open the URL Inspection tool for a sample page and it shows how Google found the URL, the last crawl date, whether robots.txt or noindex blocked it, and which canonical Google selected. Check those details before spending time rewriting content.
A Triage Process for Unindexed Contractor Pages
A fixed routine keeps the work manageable when the list is long. Follow these steps in order.
- Open Indexing, then Pages, in Search Console and select the reason you want to investigate.
- Group the listed URLs by type, such as service pages, city pages, project pages, and archives.
- Decide whether each group should be indexed at all, since some pages are better left out.
- Inspect one sample URL per group to see its crawl date, canonical, and any noindex or robots.txt block.
- Fix the cause, whether that is unique content, internal links, hosting, or sitemap cleanup.
- Request indexing for the highest-value pages only, then watch the report for several weeks.
Use Request Indexing with care. Google says a request does not guarantee the page will appear, and that each property has daily limits. For many new or updated pages, it recommends a sitemap instead. When the flagged list runs into the hundreds, contractors often hand the sorting to a team that offers contractor technical SEO support, since patterns across page types show up faster in a full crawl than in the report. Construction Marketing Services covers crawl errors, redirects, and site architecture in that work.

Pages That Should Not Be Indexed
Not every page deserves an index entry. Thank-you pages, internal search results, staging copies, login screens, and thin tag archives usually serve no search purpose, so a not-indexed status on them means the system is working. Mark them noindex deliberately and keep them out of the sitemap. Also avoid linking them prominently from the main navigation, since that sends mixed signals about which pages matter.
The risk runs the other way when a page you want ranking carries a leftover noindex from a redesign. Grouping the list by page type separates intentional exclusions from lost leads, and it keeps you from chasing pages that were never meant to appear.
Indexing, Rankings, and AI Search Visibility
Google’s guidance on AI features says pages need to be indexed and eligible to appear with a snippet, so an unindexed page is out of the running for practical AI search for contractors as well. Indexing is the first checkpoint for every form of search visibility.
Indexing is not a ranking guarantee. An indexed page still has to compete on relevance and quality. Fixes pay off most when they sit inside wider construction company SEO support that also covers content, local signals, and links, so each newly indexed page has something to rank for.
Things to Know
- Statuses in the report describe what Google did with a URL and are not penalties.
- Google says a crawled page may be indexed later, so do not resubmit it on a schedule.
- Check for a leftover noindex tag first after any redesign or migration.
- Keep the sitemap to live, indexable pages that return a normal success status.
- Fix groups of similar pages together instead of one URL at a time.
- Wait a few weeks after a fix and watch the trend before deciding it failed.
Frequently Asked Questions
What does “Crawled – currently not indexed” mean?
Google fetched the page but has not added it to its index.
Google says the page may be indexed later, so there is no need to resubmit it for crawling. Pages that stay in this status for months usually trace back to duplication, thin content, or weak internal links.
What does “Discovered – currently not indexed” mean?
Google knows the URL exists but has not crawled it yet.
Google says it often postpones these crawls when it expects they could overload the site, which is why no last crawl date appears. Weak internal links, a bloated sitemap, and slow hosting are common contributors on contractor sites.
How long does it take for a new contractor page to be indexed?
Usually about a day, though it can take a week or two.
Google’s documentation describes indexing as typically quick but not guaranteed. Linking the page from your navigation and listing it in an accurate sitemap gives Google the clearest signal to prioritize it.
Should I keep clicking Request Indexing?
No, use it sparingly and only after a real fix.
Google says a request does not guarantee the page will be indexed, and each property has daily limits. For many new or updated pages, Google recommends a sitemap instead, so repeated requests on an unchanged page rarely help.
Do all pages on a contractor website need to be indexed?
No, only pages meant to bring in search visitors should be indexed.
Thank-you pages, internal search results, staging copies, and thin tag archives can be kept out on purpose with a noindex tag. A good audit separates pages that should be excluded from pages that were excluded by mistake.
Deciding Which Unindexed Pages Earn a Second Look
Open the Pages report this week and sort the unindexed list into three piles: pages that should never be indexed, pages with a technical block, and pages Google judged not worth keeping. The first pile needs nothing. The second can usually be fixed in an afternoon. The third calls for a decision to improve, merge, or remove each page, and that decision is where the real ranking gains come from.

