Blog

Why your WordPress site isn't showing up in Google, in the order I check

By Phillip Clapham · November 7, 2026

You search for your own business and everyone else is there. Your competitor, a directory, the Facebook page you forgot about. Not your site. Every day it stays that way is a day a customer who wanted you found somebody else.

The cause is usually boring, and often it’s free to fix. Here’s the order I check it in, cheapest first.

Short answer: find out whether Google has your site at all, then look for the one setting or file telling it to stay away. On a WordPress site that’s a single checkbox more often than you’d think.

Not sure which of these is yours? Send me the address and I’ll tell you what I’d look at first.

1. Is your site actually missing?

Many people think they’re not on Google when the site is there but ranked low. So check first.

Turn off SafeSearch, then search site:yourdomain.com in Google. Results mean your site is in the index. A single page works the same way: site:yourdomain.com/the-page/ (Google Search Console Help, checked November 7, 2026).

Also search your business name in quotes. If you show up for that and not for “web design Columbus” or “plumber near me,” nothing is broken. You’re in Google and you’re not ranking for the competitive thing, which is a different problem and a longer one. I’ll come back to it at the end.

And check the calendar. If the site or the page is new, Google says it can take anywhere from a day or two to a few weeks to crawl and index it, and to allow at least a week after submitting a sitemap or an indexing request before assuming a problem (Google, checked November 7, 2026).

No results at all and the site isn’t new? Keep going.

2. The WordPress checkbox

In your dashboard go to Settings > Reading. Look for “Discourage search engines from indexing this site.” If it’s ticked, untick it and save.

WordPress’s own documentation says that since version 5.3, ticking it puts a noindex,nofollow robots tag in the head of every page, telling search engines to ignore the site (WordPress.org, checked November 7, 2026). Through 5.2 it worked another way, by serving a robots.txt that disallowed the whole site.

The usual way it ends up ticked: somebody checks it while the site is being built, so the half-finished version stays out of Google, and nobody unchecks it at launch. It’s a ten-second fix. It’s also the reason I look here first.

To see what Google sees, open any page, view the page source and search for noindex. If it’s there and the checkbox isn’t ticked, something else added it, usually an SEO plugin setting or a page-level option.

3. The robots.txt file

Go to yourdomain.com/robots.txt in a browser. If you see this:

User-agent: *
Disallow: /

then something is telling every crawler to stay out of the entire site. That’s the exact rule the old WordPress setting used to write (WordPress.org). A developer, a host or a plugin can leave it behind.

There’s a trap here worth knowing. Google’s documentation says that for a noindex rule to work, the page can’t also be blocked by robots.txt, because if the crawler can’t fetch the page it never sees the noindex (Google Search Central, checked November 7, 2026). So a site can have both problems at once and fixing only one of them changes nothing visible. Check both before deciding it’s still broken.

A noindex can also come from the server instead of the page. Google lists an X-Robots-Tag HTTP header as the other way to do it (same page), and you won’t find that one in the page source. It’s a host or plugin setting.

Robots.txt is easy to get wrong. Ahrefs says the same and, if you don’t know much about the file, tells you to hire an expert to fix it (Ahrefs). If you don’t know what’s in yours, don’t guess and edit it. This is a good moment to hand it to someone.

4. Ask Google directly

Set up a Search Console account for the site, then use URL Inspection on your home page. Google’s troubleshooting guide says that when a page isn’t indexed, the usual causes are a robots.txt block, a noindex directive, or another block such as password protection; fix it, then request indexing (Google, checked November 7, 2026).

This report is worth more than anything I could tell you from outside, because it states the reason. Everything above is me guessing the reason from the outside. This is Google saying it.

If you’ve fixed a noindex, it still won’t vanish the same day. Google has to crawl the page again to see that the rule is gone, and on a low-priority page that can take a while (Google). Requesting a recrawl in URL Inspection is the way to ask.

5. Give it a sitemap

Since WordPress 5.5 the core software publishes a sitemap index at /wp-sitemap.xml (WordPress Core, checked November 7, 2026). An SEO plugin may publish its own at a different address. Your robots.txt often lists the right one (Ahrefs, checked November 7, 2026).

In Search Console go to Sitemaps, enter the address and submit it (Ahrefs). Then make sure your important pages are linked from somewhere on your own site. A page nothing links to is hard for Google to find, and Ahrefs notes these orphan pages are rarely seen as important even when they’re in the sitemap.

6. Read the page report

Search Console’s Page indexing report sorts your URLs by status. Two of those look scary and mostly aren’t:

  • Discovered, currently not indexed. Google knows the page exists and hasn’t crawled it yet. Google’s help page says the usual reason is that it expected the crawl to overload the site and rescheduled (Google, checked November 7, 2026).
  • Crawled, currently not indexed. Google looked and chose not to include it. Google calls this common and says it doesn’t necessarily mean a problem, but if you see it for pages that matter, diagnose them with URL Inspection (same page).

For the second one, the honest answer is often that the page is thin, a near-duplicate of another, or has no links pointing to it. Fix that, and the page earns its place. No setting forces it.

7. Check it isn’t a hack

If your site shows up in Google with titles you never wrote, in a language you don’t speak, or with pharmacy words in them, that’s injected spam, and a hack can also get a site flagged or pulled. Search Console has Manual Actions and Security Issues reports that list both (Google, checked November 7, 2026). A practitioner’s tip from a WordPress agency: run the site: search and read the titles, because spam pages tend to surface there before anywhere you’d think to look (Zealous Sites, checked November 7, 2026).

If you see that, stop here and read what to do in the first hour. The same agency warns that asking Google for a security review while a backdoor is still in place just burns days.

8. Did you move or rebuild recently?

Google says a restructure, a new domain or a move to HTTPS can tank pages that used to do well if the move wasn’t done carefully. Its fix is 301 redirects from the old addresses to the new ones, and checking that both the http and https versions of your URLs aren’t showing in Google (Google, checked November 7, 2026). If you changed your site recently and the traffic fell, this is the first thing I’d look at after the checkbox.

When you’re indexed but still not showing up

Sometimes everything above is fine. You’re in the index and the phone still doesn’t ring. Two honest points.

Google’s job is to match what people want. Ahrefs puts it this way: if your pages don’t line up with what the searcher is looking for, Google won’t rank them. Look at what already ranks for the phrase you want. If those are all comparison articles and you have a services page, that’s the gap (Ahrefs).

And sites with far fewer links pointing to them than their competitors tend to struggle on competitive searches. Ahrefs says there’s no fixed number for “enough.” That’s a long project, not a ten-minute fix, and I’d rather tell you that than sell you a plugin.

Why it matters to the business

A page Google can’t list is a page that can’t bring anyone in. When the cause is one checkbox, you’ve been paying for a site that nobody could find. Sorting it takes a morning, and then the people who search for what you do can reach you without you spending anything on ads. Your staff stop hearing “I couldn’t find you online.”

When to call someone

  • You’ve unticked the box, fixed robots.txt, and Search Console still says blocked.
  • Search Console shows a security issue or a manual action.
  • You see strange pages or titles under your name.
  • You moved or rebuilt the site and traffic dropped.
  • You can’t edit robots.txt, or you don’t know who controls it. A host, a plugin and a theme can each set the rule, and the one that wins isn’t obvious.

I keep a check like this for my own site. It fails if robots.txt disallows the whole site, if a page in the sitemap is marked noindex (in the page or in the server’s response), or if a sitemap address returns an error or a redirect. It’s small and it exists because the cost of finding out late is a quiet phone.

Where I come in

Indexing and the other “can people find you” basics are part of a website audit, along with speed and security. If the problem turns out to be a compromise, that’s a rescue. Or email me the address at [email protected] and tell me what you searched. I’ll look at it and tell you whether it’s a ten-minute fix.