Pages Not Indexed by Google: A Practical Guide for Small Business WordPress Sites

If your WordPress site has pages that are not showing up in google search results, you are not alone, and you are probably losing enquiries because of it. This guide walks through the real reasons pages go missing from Google’s index, how to diagnose the problem using tools you already have access to, and a prioritised order of fixes that works for small business sites with limited time and budget.

Key Takeaways

• Start by checking Google Search Console’s page indexing report and the url inspection tool to confirm which WordPress pages are not indexed and why.
• Most missing pages are caused by simple issues: accidental noindex meta tags, robots.txt or plugin settings, weak internal links, or poor site structure.
• Fix priorities in this order: crawl blocks (robots.txt, server errors), noindex/meta tags, canonical and redirect mistakes, then content and site quality.
• For small business sites, improving internal linking, cleaning up sitemaps, and raising content quality will usually move pages from “discovered – currently not indexed” into Google’s index.
• If you get stuck, Gareth and the team at Redshaw Consulting can review your Search Console data and WordPress setup and suggest specific, practical fixes via a quick call from the contact page.

Why Your WordPress Pages Must Be Indexed To Show In Google

Google does not search the live internet every time someone types a query. Instead, it maintains its own database of web pages, and that database is the index. Before any of your website pages can appear in search results, they go through three stages: discovery (Google finds the URL), crawl (Google fetches and reads the content), and indexing (Google stores the page in its database). Only indexed pages can appear in search results and generate organic traffic.

Indexing is essential for website visibility in search engines. If a page is not indexed, it is invisible. It cannot rank for any relevant keywords, and it brings in zero search traffic. Unindexed pages are invisible to users and search engines alike, regardless of how well-designed or well-written they are.

This matters commercially. A five-page local business site in 2026 cannot afford to have its services page or contact page missing from the index. Competition is higher than it has ever been, and indexed pages contribute to a site’s overall authority and trust. Before spending time on keyword research, design tweaks, or social media, business owners should confirm that their core money pages are actually in Google’s index and eligible to rank.

Step 1: Confirm Which Pages Are Not Indexed (Using Google Search Console)

Google search console is the primary diagnostic tool for indexing issues on WordPress sites. If you have not already verified ownership of your site, do that first. Google provides several verification methods including DNS records, HTML file upload, or via your domain registrar. Once verified, the data you need is waiting.

To find out which pages google has or has not indexed, navigate to Indexing, then Pages. This opens the page indexing report, which shows your indexed and non-indexed page counts for the entire property. Google Search Console shows indexed and non-indexed page counts in a clear summary chart, with trends over time.

Below the chart, click on the reasons under “Why pages aren’t indexed.” You will see categories like:

• Discovered – currently not indexed: Google knows the URL exists but has not yet crawled it. A URL can be marked as discovered currently not indexed when Google has found it via a link or sitemap but has not prioritised fetching it.
• Crawled – currently not indexed: Google fetched the page but decided not to store it in its index. This status means Google saw the content and chose not to keep it, usually because of quality, duplication, or low perceived value.
• Alternate page with proper canonical tag: Google is indexing a different version of this page instead.
• URL marked “noindex”: a directive is explicitly telling Google not to index the page.
• Server error (5xx), Redirect errors, Soft 404: technical problems preventing normal crawl or index.

The indexed status indicates a page is successfully indexed by Google and can appear in search results.

To check specific pages, use the url inspection tool. Paste in a URL such as /services/plumbing-repairs/ and you will see whether it is indexed, the last crawl date, the canonical URL Google has selected, and any crawl or server error preventing indexing. You can also request indexing through the URL Inspection Tool for pages that need attention, though this is a request rather than a guarantee.

Keep a simple list of priority URLs that are not indexed. Focus on home, main services, contact, key location pages, and your best-performing blog posts. These are the pages that matter commercially, and they should be checked first.

Step 2: Check For Obvious Blocking Settings (noindex, WordPress, Robots.txt)

Many small business sites are blocked from indexing by accident, often after a redesign, a plugin update, or a migration from staging to live. These are usually the fastest wins.

Start with the WordPress reading settings. Go to Settings then Reading and look for the checkbox labelled “Discourage search engines from indexing this site.” If that box is checked, WordPress sends a noindex directive across your entire site. This is meant for staging or development environments. On a live site, it must be unchecked. It is one of the most common accidental blocks on small WordPress sites and affects every page.

Next, check your SEO plugin. Yoast, Rank Math, and All in One SEO all allow you to set a noindex tag on individual posts, pages, categories, tags, and archives via meta tags. A noindex tag prevents Google from indexing a page. Pages marked noindex will not appear in search results regardless of how strong the content or links are. Review these settings page by page for anything important that has been accidentally excluded.

If you want to verify directly, view the page source in your browser and search for “noindex.” You are looking for something like this:

If you find it on a page that should be indexed, the SEO plugin or theme template is the likely source. Removing noindex tags is critical for allowing those pages to be indexed.

Now check robots.txt. Open your site’s robots txt file by going to https://yourdomain.com/robots.txt in a browser. This is the file that tells search engines which parts of the site they are allowed to crawl. Blocking /wp-admin/ is normal and expected. But if you see a line like:

or

that is a problem. Robots.txt may block search engines from crawling specific pages or even your entire site. Confirming robots.txt is not blocking important pages helps facilitate indexing for those URLs.

One detail worth knowing: a URL can be indexed despite being blocked by robots.txt if other sites link to it. Google may index the URL with a limited snippet, but it cannot read the content properly. This creates a confusing situation where the page appears in results but with no useful description. The cleaner solution is always to ensure robots.txt allows crawling and to use a noindex tag only when you genuinely want a page excluded.

If the search console page indexing report shows “Blocked by robots.txt” or “URL marked ‘noindex'” for important pages, fix those settings before doing anything else. These are the highest-priority blocks because they prevent google from even considering the page.

Step 3: Fix Canonical Tags, Redirects, And Alternate Pages

A canonical tag is an HTML element that tells Google which version of a page is the preferred one. It looks like this in the page source:

When your site has multiple urls pointing to what is essentially the same page (http vs https, www vs non-www, trailing slash vs no trailing slash, URL parameters), the proper canonical tag tells Google which one to index. The others become alternate pages that Google may exclude from indexing.

Misconfigured canonical tags are a common cause of pages not being indexed. If a canonical tag on your services page points to the wrong url, or to a redirect, or to a different page entirely, Google will treat your intended page as a duplicate or alternate page. In the indexing report, these show up as “Alternate page with proper canonical tag” or “Duplicate without user selected canonical.”

To check, view the source of your WordPress page and search for rel=”canonical”. Confirm that the URL matches the clean, preferred version of that page. If your canonical points to http:// but your site runs on https://, or it points to a www version when your site uses non-www, that is a mismatch that can confuse search engines.

Redirect issues are equally damaging. Common WordPress redirect problems include:

• Redirect loops where URL A redirects to URL B which redirects back to URL A. Redirect loops can prevent Googlebot from indexing pages entirely.
• Long redirect chains where a URL passes through three or four url redirects before reaching the final destination. Redirect chains waste crawl budget and should be minimised.
• Old URLs from a previous site structure that were never mapped with 301 redirects, leaving them as 404 errors or pointing to generic parent pages.

Changes in URL structure during a redesign can disrupt indexing significantly. If you moved from /services/boiler-installation to /our-services/boiler-install without setting up a redirect, the old indexed URL now returns a 404 and the new one may take weeks to be discovered and indexed.

Use a simple HTTP status checker or browser extension to verify that any redirect url returns a single 301 to the final destination, and that the final destination is crawlable and not noindexed. Duplicate content can result in Google indexing only the original version, so cleaning up duplicate pages and duplicate or alternate pages with correct canonical tags usually restores normal search rankings.

Gareth at Redshaw Consulting often finds indexing issues caused by page builders duplicating templates or plugins generating alternate URLs that were never intended to exist. Cleaning those up, setting correct canonicals, and mapping redirects properly resolves a surprising number of cases.

Step 4: Improve Crawl Discovery: Site Structure, Internal Linking, And Sitemaps

Even when pages are technically allowed to be indexed, Google must be able to discover and crawl them. A sensible site structure and strong internal linking structure make this possible.

Good small business site structure follows a clear hierarchy. The home page links to main service categories. Each category links to individual service detail pages. Blog posts link back to related services. Navigation menus, footer links, and sidebar elements reinforce these connections. This is how Google crawls your site efficiently and understands which pages matter most.

Orphan pages are a common problem. These are pages that lack internal links pointing to them. A landing page only reachable from an email campaign link, or a service page that was removed from the navigation during a redesign, becomes an orphan. Orphan pages lack internal links, hindering indexing. They often appear in Search Console as discovered currently not indexed because Google found them in a sitemap or external link but has no internal context to prioritise crawling them.

To fix this, build internal links deliberately:

• Link new blog posts to your main service pages using descriptive anchor text like “gas boiler servicing in Leeds” rather than “click here.”
• Add “related services” or “related articles” sections to the bottom of key pages.
• Ensure your navigation menu includes all important pages.
• Check that internal links pointing to other pages use consistent URLs (not mixing http/https or www/non-www).

Poor internal linking is one of the most overlooked causes of indexing failures on small sites. Adding even two or three internal links from strong, already-indexed pages to a non indexed page can be enough to prompt Google to crawl and index it.

A sitemap helps Google discover important pages on your site. Most SEO plugins (Yoast, Rank Math) automatically generate an XML sitemap at /sitemap.xml. Submit this in the Sitemaps section of Search Console. A clean sitemap helps Googlebot prioritise important pages by listing only live, canonical, 200 OK URLs. If your sitemap includes redirected URLs, noindexed pages, 404 errors, or thousands of thin tag archives, it dilutes crawl focus and sends mixed signals.

Crawl budget is the number of pages Googlebot can crawl within a given timeframe. For most small WordPress sites with under a few hundred pages, crawl budget is not a serious constraint. Sites with over one million pages need active crawl budget management. But even on smaller sites, bloated sitemaps full of low-value archive URLs can lead to many pages staying in discovered currently not indexed while Google spends its time on pages that do not matter. Blocking low-value pages from the sitemap and from crawling can improve crawl budget efficiency, letting Google focus on the pages that drive revenue.

Step 5: Address Content Quality, Thin Pages, And Overall Site Quality Signals

Google applies site quality thresholds when deciding what to keep in its index. Content quality became the dominant indexing factor in 2025, and in 2026 that trend has only intensified. Google may not index pages with low-quality content, regardless of whether they are technically crawlable.

Thin content in a WordPress context includes:

• Service pages with only two or three generic sentences.
• Product descriptions copied from manufacturer websites.
• Blog post stubs from years ago with almost no detail.
• Location pages where only the city name changes between otherwise identical text.

These are frequently excluded under crawled currently not indexed status. Google fetched the page, read the content, and decided it was not worth storing. A study of 16 million pages by IndexCheckr found that approximately 62% were never indexed, with most exclusions driven by content quality, duplication, or low perceived value.

Duplicate content google identifies as redundant will typically result in only the original version being indexed. If you have five location pages with nearly identical text, Google will likely pick one and exclude the rest. Similarly, automatically generated category and tag pages with the same post excerpts can create large numbers of duplicate pages that waste index space.

Common reasons for Google not indexing web pages include technical blocking and low-quality content, but a weak backlink profile can also slow down or prevent indexing. Pages with no external links pointing to them and weak internal link equity are less likely to be prioritised. This does not mean you need to buy links. It means that earning mentions, local citations, or industry directory listings supports indexing over time, alongside content improvements.

Search engines, including Google, evaluate signals such as core web vitals, spammy patterns, keyword stuffing, and unnatural links when assessing pages. Structured data, while not a direct ranking or indexing factor, helps Google understand page content and can influence how pages appear in results.

Enhancing content quality will help prioritise indexing by Google. The practical approach for small business sites is to consolidate thin or overlapping content into fewer, more comprehensive pages. Write each page to directly answer common customer questions, include local examples, use clear headings, and provide enough depth to be genuinely useful. Improving site quality can turn a cluster of “Crawled – currently not indexed” pages into stable indexed URLs over several weeks as Google’s algorithms reassess the site.

Research also suggests that non-refreshed blog content has an index half-life of roughly 11 months, meaning content that is not updated may gradually fall out of Google’s index. Plan content refreshes accordingly, particularly for posts older than six to eight months.

Step 6: Fix Server Errors, Performance, And Technical Reliability

The page indexing report in Search Console flags technical problems such as server error (5xx), Soft 404, and Crawl anomaly. These often point to hosting or configuration issues that prevent google from completing its crawl.

Intermittent server errors during crawls reduce Google’s crawl rate for your site and keep pages stuck in discovered currently not indexed. This is common on shared or budget hosting where resources are limited and server response times spike during peak traffic or heavy crawl periods.

Check your hosting dashboard or server logs for patterns:

• 500 errors during specific times of day.
• Connection timeouts when multiple requests hit the server simultaneously.
• Resource limits reached on shared hosting plans.

If you find consistent issues, consider optimising WordPress (removing unused plugins, implementing object caching) or moving to a more reliable hosting plan with HTTP/2 support and better uptime.

Google uses mobile-first indexing, which means it primarily uses the mobile version of your site for crawling and indexing. Mobile usability is important for ensuring proper indexing by Google. If your WordPress theme renders poorly on mobile, hides content behind JavaScript that does not execute properly, or has layout issues on smaller screens, this affects how Google sees and evaluates your pages.

Slow loading and poor core web vitals scores will not directly prevent indexing, but they contribute indirectly. Heavy themes like Avada with unoptimised configurations, oversized images, and excessive plugin loads can make crawling less efficient and hurt search rankings over time. Simple speed improvements include:

• Installing a caching plugin (WP Super Cache, LiteSpeed Cache).
• Compressing and resizing images before upload.
• Removing or deactivating plugins you are not using.
• Ensuring your hosting plan provides solid server response times.

Gareth and Redshaw Consulting often start any technical SEO work by checking hosting stability, since solving server error patterns can unlock faster and more complete indexing across the entire site. If your pages report persistent 5xx errors or crawl anomalies, no amount of content improvement will help until the underlying server issue is resolved.

Step 7: Prioritised Fixes For Small Business WordPress Owners

If you have read this far and feel overwhelmed by the number of potential issues, here is a practical order of operations that works for small WordPress sites:

1. Confirm index status in search console. Use the page indexing report and url inspection tool to identify affected pages and affected urls. Know which specific pages are missing and why.
2. Remove accidental blocks. Uncheck “Discourage search engines” in WordPress settings. Review SEO plugin settings for any noindex tag on pages that should rank. Fix your site’s robots txt file if it blocks important directories.
3. Repair redirects and canonical tags. Ensure every canonical tag points to the correct, clean URL. Fix redirect loops and chains. Map old URLs to new ones with 301 redirects if you have changed site structure.
4. Improve internal linking and sitemaps. Add internal links from strong pages to weak ones. Remove orphan pages from isolation. Clean your XML sitemap so it only lists canonical, live URLs. Submit or resubmit the sitemap in Search Console.
5. Upgrade content quality and performance. Rewrite thin pages. Consolidate duplicates. Improve page speed and mobile usability. Fix server errors.

Focus on revenue-critical pages first. Your home page, core services, local area pages, testimonials, and contact page should be the priority. Do not waste time worrying about every old blog post or tag archive before your money pages are sorted.

After implementing changes, revisit the pages report and index coverage report two to four weeks later. Look for movement from “not indexed” to “indexed” on your priority URLs. Google rescheduled crawls of your site based on the signals it receives, so changes are not instant. Allow time for the crawl date to update and for Google to reassess.

After content updates, request Google to recrawl the page using the url inspection tool. Use the “Request indexing” option sparingly and only for high-priority individual pages after technical issues are resolved. Do not spam requests for every URL. You can also validate fix actions in Search Console for categories of issues, which tells Google to recheck affected urls.

If multiple pages remain stuck, look at whether the problem is site-wide (a template issue, a plugin conflict, a hosting problem) rather than page-specific. Wrong pages being indexed while important pages are excluded often points to canonical or link equity distribution problems.

If you are still stuck after working through these steps, or if you have seen a sudden drop in the number of indexed pages that you cannot explain, Gareth at Redshaw Consulting can review your actual Search Console data and WordPress setup. A structured action plan based on real diagnostics is far more effective than guessing. Reach out through the contact page to start that conversation.

FAQ

How long does it usually take for a new WordPress page to be indexed?

On a typical small business site in 2026, Google crawls new pages within a few days of discovery and indexes them within a few days to a few weeks, depending on site authority and how well the page is connected. Linking new content from the home page or a main services page and ensuring it appears in the XML sitemap speeds up discovery significantly. Using the url inspection tool to request indexing can help, but it does not guarantee same-day results. For a new site with little authority, expect the process to take longer, sometimes several weeks for pages to move from discovered to indexed.

What does “Crawled – currently not indexed” really mean for my site?

This status in the indexing report means Google has seen the page content but has chosen not to keep it in the index at this time. On small business sites, the most common causes are weak or duplicate content, very similar location pages with only city names swapped, or low perceived value compared with other pages on the site or on competing sites. To address it, improve the depth and uniqueness of the page, add internal links from strong pages, ensure it serves a genuine user need, and then wait a few weeks before checking the indexing status again. There is no way to force Google to index a page it considers low value.

Should I noindex WordPress tag and category pages?

Many small WordPress sites benefit from noindexing thin tag archives that list only one or two posts. These pages add little value and can dilute crawl budget away from service pages and key blog posts. Use your SEO plugin settings to selectively noindex low-value archives. However, if certain category pages have substantial unique introductions, useful link equity, and a clear purpose for visitors, they can be worth keeping indexed. The key distinction is whether the archive page serves a real user purpose or just exists because WordPress created it automatically.

Can changing themes or builders cause pages to drop out of the index?

Yes, and it happens frequently. Site redesigns, switching from one WordPress theme to another, or moving to a different page builder can change URLs, headings, meta tags, navigation structure, and internal links all at once. These changes can accidentally introduce noindex tags on templates, create broken redirects, generate new duplicate pages, or remove internal links that previously supported indexing. Recovery from a redesign typically takes four to twelve weeks if the technical signals are restored promptly. Run a post-migration check in Search Console, compare the site before and after using a crawl tool, and review key templates carefully. If larger drops appear, working with Gareth or another technical specialist can identify issues that are not obvious from the surface.

When should I ask for professional help with indexing problems?

Seek help when core pages like your home page, contact page, and main service pages remain unindexed for more than four to six weeks despite resolving obvious blocks. A sudden drop in the number of pages indexed around the same date, visible in the page indexing report, can signal a wider technical or quality issue that is worth expert review. If you are seeing patterns you cannot explain, or if multiple fixes have not moved the needle, sharing access to your Search Console and WordPress dashboard with Redshaw Consulting lets Gareth pinpoint the real cause based on actual data rather than guesswork. You can start that process through the contact page.