How to Fix a WordPress Site That Is Not Showing Up in Google 

You open a new browser tab, type your website name into Google, and nothing comes up.

Not buried on page five. Not ranking low for your target keywords. Just completely, utterly absent.

That feeling is somewhere between confused and panicked, and if you are reading this, you probably know exactly what it feels like.

The good news is this: in the vast majority of cases, a WordPress site that is not showing up in Google is not broken. It is blocked. Or it has not been properly introduced to Google yet. Or it has a small technical setting that is quietly telling search engines to stay away.

Every single one of those situations is fixable. Most of them are in under ten minutes.

This guide walks through every real reason a WordPress site goes missing from Google, in order from most common to least common, with clear steps to diagnose and fix each one. By the end, you will know exactly what is wrong with your site and exactly how to resolve it.

How Google Finds and Shows Your Website

Before troubleshooting, it helps to understand the three-stage process Google uses to get your site into search results. A problem at any one of these stages will cause your site to go missing.

Stage 1: Crawling

Googlebot, Google’s automated web crawler, discovers your pages by following links and reading your sitemap. If crawling is blocked by robots.txt, a server error, or a missing sitemap, Google never reads your content in the first place.

Stage 2: Indexing

After crawling, Google decides whether to add your pages to its index. A noindex tag, a canonical pointing to another URL, thin content, or duplicate content can all cause Google to crawl a page but choose not to index it.

Stage 3: Ranking

Even after indexing, Google must decide where to rank your page for relevant searches. If your site is not appearing in results at all for a specific keyword, the question is whether the page is not indexed, or whether it is indexed but not ranking well enough to be visible.

Understanding which stage has broken down tells you exactly where to look for the fix. The sections below are organised in this order: blocking issues first (stages one and two), then ranking and visibility issues after.

Before You Troubleshoot: Run This Quick Check First

Before diving into individual fixes, start with one command that tells you immediately whether Google has indexed your site at all.

Open Google and type exactly this into the search bar:

site:yourwebsite.com

Replace yourwebsite.com with your actual domain.

What the result tells you:

• Results appear: Google has indexed at least some of your pages. The issue is likely a ranking or specific page problem rather than a site-wide crawling or indexing block.
• No results appear: Google has either not crawled your site yet or something is actively preventing indexing. Work through this guide from the beginning.
• Only a few pages appear: Some pages are indexed but others are not. Use Google Search Console’s URL Inspection tool on the missing pages to identify the specific cause.

Keep this result in mind as you read through each reason below.

Reason 1: WordPress Is Blocking Search Engines at the Source

This is the single most common cause of a WordPress site disappearing from Google, and it is almost always accidental.

WordPress has a native setting that tells search engines not to index your site. It lives under Settings > Reading in your WordPress dashboard and is labelled “Discourage search engines from indexing this site.”

Developers tick this checkbox during the build phase to keep an unfinished site private. The overwhelming majority of the time, they simply forget to uncheck it before launch.

One checked the checkbox. Your entire site is blocked from Google. This is found on a significant proportion of sites that come in for technical SEO audits with “not showing up” complaints.

How to fix it:

• Go to your WordPress dashboard
• Navigate to Settings > Reading
• Scroll to the Search Engine Visibility section
• Confirm the “Discourage search engines from indexing this site” checkbox is unchecked
• Click Save Changes

After unchecking, allow one to three days for Google to begin crawling again. Use the URL Inspection tool in Google Search Console to request indexing of your most important pages immediately.

How SureRank helps: SureRank’s site-wide SEO audit checks this setting as part of its standard indexability checks. If your site has this box ticked, SureRank flags it as a critical issue in the audit report, which is visible the first time you run the analysis after installation.

Run a site SEO audit with SureRank.

Reason 2: Your Site Has a Noindex Tag on Important Pages

Even if the site-wide WordPress setting is correct, individual pages can still be set to noindex through your SEO plugin.

A noindex directive tells Google: “Do not include this page in search results.” It is a legitimate and useful tool for keeping low-value pages (login pages, thank-you pages, admin pages) out of the index. The problem occurs when it is applied to pages you actually want to rank, which happens during migrations, redesigns, and plugin changes more often than you would expect.

What noindex looks like in the code:

If a page has a noindex tag applied, Google will see something like this in the page’s head section:

<meta name=”robots” content=”noindex”>

Google sees this, respects it, and excludes the page from search results. No warning. No notification.

How to find noindex pages:

Method 1: Google Search Console

• Open Search Console
• Go to Indexing > Pages
• Look under “Why pages aren’t indexed” for the entry labelled “Excluded by noindex tag”
• Click it to see which specific pages are affected

Method 2: SureRank meta box

• Open any post or page in WordPress
• Scroll to the SureRank meta box
• Check the Advanced tab
• Confirm the indexing setting is set to Index and not Noindex

Method 3: Check site-wide SEO plugin settings

Many SEO plugins allow you to set noindex globally for certain post types, archive pages, or tag pages. In SureRank, navigate to the global settings for each content type and confirm the default indexing behaviour is set correctly for all post types you want Google to find.

How to fix it in SureRank:

• Open the post or page that is missing from Google
• Scroll to the SureRank meta box in the editor
• Go to the Advanced tab
• Under Search Engine Visibility, confirm Index is selected
• Update the page
• Use Search Console’s URL Inspection tool to request re-indexing immediately

How SureRank helps: SureRank’s on-page meta box shows the indexing status clearly for every post and page from inside the editor. The site-wide audit flags any pages where noindex is applied unexpectedly. As of SureRank 1.8.0, the Google Search Console URL Inspection status is visible directly inside the SureRank meta box for each post, so you can confirm indexing status without leaving WordPress.

Read how to manage indexing settings in SureRank.

Reason 3: Your Robots.txt File Is Blocking Googlebot

Your robots.txt file is a small text file that sits at the root of your domain (yoursite.com/robots.txt) and tells search engine bots which parts of your site they are allowed to crawl.

A correctly configured robots.txt file is harmless. A misconfigured one can block Googlebot from crawling your entire site, or from crawling specific sections, without any visible warning on your end.

The most dangerous misconfiguration looks like this:

User-agent: *

Disallow: /

That single line blocks every crawler from accessing every page on your site. It is the digital equivalent of locking the front door and throwing away the key.

Less severe but still damaging configurations might block specific directories that your important pages live in, or block the URLs where your CSS and JavaScript files are stored (which can make your pages appear broken to Google).

How to check your robots.txt:

• Visit yoursite.com/robots.txt in your browser
• Read the Disallow rules carefully
• Check whether any rules are blocking pages or directories you want Google to crawl

Warning signs to look for:

• Disallow: / under User-agent: * blocks your entire site
• Disallow: /wp-content/ blocks your theme and plugin files
• Any Disallow rule that matches the path of your important pages

How to fix it in SureRank:

SureRank includes a built-in robots.txt editor so you never have to edit the file directly via FTP.

• Go to SureRank > General > Robots.txt in your WordPress dashboard
• Review the current rules
• Remove or edit any Disallow directives that are blocking pages you want indexed
• Confirm your sitemap URL is referenced in the file with a line like: Sitemap: yoursite.com/sitemap_index.xml
• Save changes

After fixing the robots.txt, use Google Search Console’s URL Inspection tool to request crawling of your most important pages.

Read the SureRank Robots.txt documentation.

Reason 4: Your Site Has No XML Sitemap or It Is Broken

An XML sitemap is a file that lists every important URL on your site and tells Google where to find them. Without one, Google discovers your pages only by following links, which is slower, less reliable, and means any page that is not well-linked internally may never be found.

A missing, outdated, or broken sitemap is one of the most common causes of slow or incomplete indexing, particularly for newer sites and pages that do not have strong internal link coverage.

How to check your sitemap:

• Visit yoursite.com/sitemap_index.xml in your browser
• If you see an XML file listing your content, your sitemap is active
• If you see a 404 error or a blank page, your sitemap is missing or broken

Also check in Google Search Console:

• Go to Indexing > Sitemaps
• Check the status of any submitted sitemaps
• A green “Success” status with a recent fetch date means Google is reading your sitemap correctly
• A “Could not fetch” status means Google cannot access it

Common sitemap problems:

• Sitemap toggle disabled in your SEO plugin settings
• Caching plugin serving an old cached version that returns an error
• Post types excluded that should be included
• Sitemap URL submitted to Search Console is incorrect or outdated

How to fix it in SureRank:

• Navigate to SureRank > General > Sitemaps
• Confirm the Enable XML Sitemap toggle is switched on
• Click Regenerate to rebuild the sitemap fresh
• Clear your caching plugin if you use one
• Visit yoursite.com/sitemap_index.xml to confirm it loads correctly
• Submit or resubmit the sitemap URL in Google Search Console

SureRank generates your XML sitemap automatically from installation and keeps it updated every time you publish, update, or delete content. It also includes image data, author archive pages (added in version 1.9.0), and post-type archive pages within the sitemap automatically.

Read the complete SureRank sitemap documentation.

See the full guide to setting up and submitting your WordPress sitemap.

Reason 5: Google Has Not Crawled Your Site Yet

Sometimes there is no mistake. No misconfiguration. No blocked setting.

Your site simply has not been found yet.

For brand-new domains, Google may take anywhere from several days to several weeks to discover and begin crawling a site for the first time. This timeline is influenced by how many external sites link to you, how active your sitemap submission is, and how often you publish new content.

A site with zero inbound links, no sitemap submitted to Search Console, and no new content published since launch may genuinely wait weeks before Googlebot pays its first visit.

How to speed up initial discovery:

• Submit your sitemap URL to Google Search Console immediately. Do not wait.
• Use Search Console’s URL Inspection tool to request indexing for your most important pages directly.
• Get at least one external link pointing to your homepage, even from a directory listing or social media profile. This gives Googlebot a path to follow.
• Publish new content regularly. Active sites get crawled more frequently than static ones.

How SureRank’s Instant Indexing solves this permanently:

SureRank Pro includes Instant Indexing, which notifies search engines directly the moment you publish or update any page. Instead of waiting for Google’s next scheduled crawl, which could be days away, SureRank fires a ping to IndexNow the instant you hit publish.

IndexNow is supported by Bing, Yandex, and other major search engines. For Google specifically, SureRank Pro also supports the Google Indexing API directly.

What this looks like in practice:

• Enable Automatic Indexing in SureRank > Advanced > Instant Indexing
• Flip the toggle on and save
• Every post you publish from that point triggers an immediate notification to search engines
• The Logs page inside Instant Indexing shows the timestamp, URL, and response for every submission so you can verify it is working

For existing content backlogs:

• Open your Posts or Pages list in WordPress
• Select the posts you want indexed
• Choose “Submit to IndexNow” from the Bulk Actions dropdown
• SureRank submits the entire selection in one pass

You can also paste up to 100 URLs at once in the Bulk Indexing tab inside the Instant Indexing settings for batch submission.

See SureRank’s Instant Indexing feature in detail.

Reason 6: Your Site Is Not Connected to Google Search Console

Google Search Console is the direct communication channel between Google and your site. Without it, you are essentially flying blind.

Search Console tells you which pages are indexed, which are not and why, whether Google has encountered any crawl errors, how your pages are performing in search, and whether you have received any manual penalties.

If your site is not connected to Search Console, you have no way of knowing what Google is seeing when it visits your site or what is preventing your pages from appearing in search results.

How to connect your site to Google Search Console:

• Go to search.google.com/search-console and sign in with your Google account
• Add a new property using your domain URL
• Complete the verification process using the HTML tag method, DNS verification, or your SEO plugin’s verification field
• Once verified, submit your sitemap URL under Indexing > Sitemaps
• Check the Pages report under Indexing to see the current status of your site’s indexed and non-indexed pages

How SureRank integrates with Search Console:

SureRank connects directly to Google Search Console and surfaces performance data inside your WordPress dashboard. You can see clicks, impressions, CTR, and average position for every page without leaving WordPress.

As of SureRank 1.8.0, the URL Inspection status for each individual post or page is visible directly inside the SureRank meta box in the editor. This means you can check whether any specific page is indexed without logging into Search Console separately.

Connect SureRank to Google Search Console.

Reason 7: Pages Are Being Crawled But Not Indexed

This is one of the more frustrating situations: Google is visiting your pages but actively choosing not to include them in the index.

In Google Search Console, this shows up as “Crawled, currently not indexed” in the Pages report under Indexing. Google has read the page but decided it is not worth including in search results.

Common causes:

• Thin content: Pages with very little original content are routinely skipped. A page with fewer than 300 words of substantive content, or a page that mostly duplicates another page, is a common target for this status.
• Duplicate content: If multiple URLs on your site deliver the same or very similar content, Google indexes one and ignores the rest.
• Low quality signals: Pages with no internal links pointing to them (orphan pages), no images, no structured information, and no engagement signals are judged as low value.
• Slow page speed: Pages that take more than three to four seconds to load on mobile may be crawled but deprioritised for indexing.
• Wrong canonical tag: A canonical tag pointing to a different URL tells Google to index that other URL instead. If the canonical is set incorrectly, your page gets excluded.

How to fix it:

• Open Search Console and check the specific reason listed under “Why pages aren’t indexed” for each affected page
• For thin content: expand the page with original, substantive content. Aim for thorough topic coverage.
• For duplicate content: consolidate similar pages or set proper canonical tags pointing to the authoritative version
• For orphan pages: add internal links from relevant existing content using SureRank’s Link Manager
• For wrong canonicals: open the SureRank meta box on the affected page and check the Advanced tab for any incorrect canonical URL setting

How SureRank helps: SureRank’s site-wide SEO audit surfaces pages that are crawled but not indexed and flags the likely cause. For many common issues, SureRank Pro offers one-click AI fixes that resolve the problem immediately.

Run your site-wide SEO audit with SureRank.

Reason 8: Duplicate Content or Canonical Tag Issues

Duplicate content is when the same or substantially similar content appears at multiple URLs on your site. Google has to decide which version to index. It usually picks one and ignores the rest, which means your preferred page may be the one getting ignored.

Common sources of duplicate content in WordPress:

• Category and tag archive pages that replicate post content
• Pagination pages (page/2, page/3) that repeat the same post titles and excerpts
• WWW versus non-WWW versions of your site both being accessible (yoursite.com and www.yoursite.com serving the same content)
• HTTP versus HTTPS versions both being accessible
• Printer-friendly or mobile versions of pages served at separate URLs
• URL parameters from tracking or filtering (yoursite.com/product/?color=red and yoursite.com/product/?color=blue serving the same product)

How to fix it:

• WWW and non-WWW: Set a preferred version in Google Search Console and ensure your WordPress Address and Site Address under Settings > General both use the same format consistently
• HTTP and HTTPS: Confirm your SSL certificate is active and that all HTTP requests redirect to HTTPS
• Canonical tags: Use canonical tags to indicate the preferred version for any page that exists at multiple URLs

How SureRank helps: SureRank automatically sets canonical tags for every page based on your site’s configuration. The site-wide audit checks for canonical inconsistencies across your site and flags pages where the canonical URL does not match the page URL. You can view and edit the canonical for any individual page from the Advanced tab in the SureRank meta box.

Reason 9: Your Site Has a Manual Penalty from Google

Google’s human review team occasionally issues manual actions (also called manual penalties) against sites that violate Google’s spam policies. These include practices like keyword stuffing, hidden text, unnatural link patterns, cloaking, and thin content created at scale.

A manual penalty can cause a site to drop significantly in rankings or be removed from the index entirely for the affected pages.

How to check for a manual penalty:

• Open Google Search Console
• Go to Security and Manual Actions > Manual Actions
• If a manual action exists, it is listed here with a description of the violation and which pages are affected

How to fix it:

Manual actions require you to identify and resolve the specific violation described in the Search Console notice, then submit a reconsideration request explaining the changes you have made. Google reviews the request and lifts the action if the issue has been genuinely resolved.

Manual penalties are less common than technical issues but worth checking, especially if your site previously ranked well and suddenly disappeared from results.

Reason 10: Your SSL Certificate Has Lapsed or Is Misconfigured

Google treats HTTPS as a trust signal. Sites without a valid SSL certificate are flagged as insecure in browsers and are deprioritised in search rankings. In some cases, an expired or misconfigured SSL certificate can cause Googlebot to encounter errors when trying to access your site, which leads to crawling problems.

How to check:

• Visit your site in a browser and look at the address bar
• A padlock icon indicates a valid SSL certificate
• A warning message (“Not Secure” or a certificate error) indicates a problem
• Your hosting control panel shows the SSL certificate status and expiry date

How to fix it:

• Renew the SSL certificate through your hosting provider if it has expired
• Most modern hosting providers offer free SSL certificates through Let’s Encrypt that renew automatically
• After renewing, confirm that HTTP requests redirect to HTTPS at Settings > General in WordPress

Reason 11: Your Site Is Too New

This one is not a mistake. It is simply how Google works.

A brand-new domain with no backlinks, no publishing history, and no Search Console verification will take time to gain Google’s trust and appear in search results. Even after initial indexing, new sites typically take three to six months of consistent content publishing before they rank meaningfully for competitive keywords.

What “too new” looks like in Search Console:

• Low or zero impressions in the Performance report
• A small number of indexed pages relative to the number you have published
• “Discovered, currently not indexed” status for many pages (Google knows they exist but has not prioritised crawling them yet)

What to do:

• Submit your sitemap to Google Search Console and request indexing for your most important pages
• Publish new content consistently. Sites with regular publishing activity get crawled more frequently.
• Build at least a few quality backlinks. Even a single link from a trusted external site accelerates crawling and trust-building.
• Use SureRank Pro’s Instant Indexing to ensure every piece of new content gets immediately notified to search engines rather than waiting for the next scheduled crawl.

This phase requires patience alongside the right actions. The sites that make it through this period are the ones that keep publishing, keep building authority, and trust the process.

Read the complete guide to building SEO for a new WordPress site.

Reason 12: You Are Ranking, Just Not Where You Think

Sometimes a site is indexed and ranking, but the person checking cannot find it because they are looking in the wrong place.

A few situations where this happens:

• Personalisation: Google personalises search results based on your location, browsing history, and login status. Your site may appear at position 14 for someone in a different city who has never visited your site before, while showing much higher for you.
• Location targeting: If your site is targeted at a specific country or region, it may rank well in that region and not appear at all in searches from other locations.
• Competitive keywords: Your site may be indexed and ranking for your exact keywords, but at position 40 rather than position 10. A site:yoursite.com search confirms indexing. Poor ranking for competitive terms is a different problem entirely.

How to check accurately:

• Use Google Search Console’s Performance report to see exactly which queries are triggering impressions for your site and at what average position
• Use an incognito browser window to reduce personalisation effects when manually checking rankings
• Use the URL Inspection tool to check specific URLs rather than relying on general search visibility

How SureRank Prevents All of These Problems Automatically

Every cause covered in this guide falls into one of three categories: something that was misconfigured, something that was never set up, or something that needs ongoing monitoring. SureRank addresses all three.

On install, SureRank handles:

• XML sitemap generation, live immediately after the setup wizard
• Core schema markup applied to all content types automatically
• Open Graph and social metadata configured correctly from day one
• Canonical tags set correctly for every page
• Organisation and WebSite structured data applied using your brand details

The site-wide SEO audit surfaces:

• Accidental noindex settings on pages that should be indexed
• Pages missing from the sitemap
• Broken or missing canonical tags
• HTTPS and redirect configuration issues
• Pages with no meta descriptions or duplicate meta titles

In SureRank Pro, the AI can suggest and apply fixes for many of these issues in a single click.

Instant Indexing eliminates crawl delays:

Every time you publish or update a post, SureRank Pro fires a ping to IndexNow, notifying Bing, Yandex, and other IndexNow-supported engines immediately. The logs page records every submission with timestamp, URL, and response code so you can verify every notification was successful.

The robots.txt editor keeps your configuration clean:

SureRank’s built-in robots.txt editor lets you view and edit your crawl directives from inside WordPress without FTP access. The editor also ensures your sitemap URL is correctly referenced.

Google Search Console integration brings visibility inside WordPress:

The URL Inspection status is visible inside the SureRank meta box for every post. Search performance data including impressions, clicks, and average position is visible in the WordPress dashboard. You do not need to log into a separate platform to understand how Google sees your site.

Download SureRank free and fix your site’s indexing issues today.

SureRank Pro with Instant Indexing, AI-powered site audit fixes, and the full technical SEO stack starts at $99 per year for up to 10 sites.

Your Complete Troubleshooting Checklist

Work through this list in order. Most sites have their problem identified within the first four items.

Step 1: The site:yourwebsite.com check

• Open Google and search site:yourwebsite.com
• Note whether results appear and how many pages are indexed

Step 2: WordPress search engine visibility setting

• WordPress Dashboard > Settings > Reading
• Confirm “Discourage search engines from indexing this site” is unchecked

Step 3: Individual page noindex settings

• Open your most important pages in WordPress
• Check the SureRank meta box > Advanced tab > confirm Index is selected
• Check SureRank’s global settings to confirm no post types are set to noindex by default

Step 4: Robots.txt file

• Visit yoursite.com/robots.txt in a browser
• Check for any Disallow: / or other blocking rules
• Edit via SureRank > General > Robots.txt if needed

Step 5: Sitemap status

• Visit yoursite.com/sitemap_index.xml in a browser
• Confirm it loads and contains your pages
• Check the sitemap status in Google Search Console > Indexing > Sitemaps

Step 6: Google Search Console setup

• Confirm your site is verified in Search Console
• Check the Pages report under Indexing for any issues
• Submit your sitemap URL if not already done
• Use URL Inspection on your most important pages

Step 7: Search Console URL Inspection

• Open Search Console or the SureRank meta box for any specific page
• Check whether the page is indexed and when it was last crawled
• Request indexing if the page is not yet indexed

Step 8: Manual actions check

• Search Console > Security and Manual Actions > Manual Actions
• Confirm no manual penalties are active

Step 9: SSL certificate

• Check your site URL in a browser for the padlock icon
• Confirm HTTP redirects to HTTPS correctly

Step 10: Enable Instant Indexing for future content

• SureRank Pro > Advanced > Instant Indexing
• Enable Automatic Indexing
• Use Bulk Submit for any existing content not yet indexed

Frequently Asked Questions