You hit publish, checked Google a few hours later, and your website was nowhere to be found. Frustrating, right? Before you panic, take a breath. Google usually is not ignoring your site on purpose. Most of the time, a small setting, a missing file, or a simple technical hiccup is keeping your pages out of search results.
In this beginner-friendly guide, we will walk through 12 things to check when your website is not showing on Google. We will start with a Quick Triage to help you find out why Google cannot see your site. Then we will look at the most common culprits one by one: whether your site is actually in Google’s index, what the URL Inspection tool says, robots.txt blocks, accidental noindex tags, WordPress settings, XML sitemaps, redirects and 404s, canonical tags, firewall or security plugins, manual actions in Search Console, brand-new pages, and big site wide blockers like SSL, downtime, and DNS.
By the end, you will have a clear action plan to get your site back into Google, without needing to be an SEO expert.
Quick Triage: Find Out Why Google Cannot See Your Site
A live website can be invisible on Google, and Google’s own guidance says most sites have at least a few unindexed pages. That’s normal, not a disaster. New to this? Our SEO education library covers the basics.
Start simple: search site:yourdomain.com. Zero results usually means an access problem (robots.txt, firewall, server) or a brand new site Google hasn’t crawled yet. Google’s guidance notes sites under 500 pages probably don’t need the Page Indexing report; site: searches are quicker.
Work in order so you don’t chase the wrong problem: access blockers first (robots.txt, firewall, SSL, DNS), then page-level tags (noindex, canonical), then submission (sitemap, request indexing), then status issues (manual actions, downtime).
Indexing isn’t instant and varies by site and page. No tool, plugin, or consultant can promise a date. If your site is invisible on Google, keep a short log: the date you changed each setting, plus what a live test showed. It makes troubleshooting far faster later.
1. Is Your Site Actually in Google’s Index?
Those results are more useful than they look. A site:yourdomain.com search gives a rough sample of what Google knows about, not an exact count, since Google’s figures are approximations. To test a topic, add keywords: site:yourdomain.com web design. Nothing for a service you offer means that page isn’t being picked up. For one page rather than the whole domain, use Google’s URL Inspection tool to inspect a specific page.
Zero results often means a crawl block, a noindex tag, a very new site, or a domain that recently changed hands. Remember, Search Console’s Page Indexing report caps its example URL list at 1,000 items. A page can be missing there and still be fine. If you’d rather hand the diagnosis over, see how Canadian small businesses should evaluate SEO services before signing a contract. A proper technical SEO audit covers all of this.
2. What the URL Inspection Tool Says About One Page
Your site: search gave a rough answer. For one page, use URL Inspection. The Page Indexing report doesn’t investigate individual pages; URL Inspection reads the index for one URL.
Paste the exact URL, https and trailing slash included, then read the verdict: “URL is on Google” or “URL is not on Google.” “URL is on Google” means the page is eligible to appear, not that it will.
Coverage details show whether crawling and indexing were allowed, and whether Google’s chosen canonical matches yours. Test Live URL shows the page as Googlebot crawls and renders it right now, the fastest way to confirm a fix worked before the next crawl.
Request Indexing queues the URL for a fresh crawl. It is a request, not an instruction, and guarantees nothing about indexing or ranking. Persistent issues may need SEO consulting help.
3. Is robots.txt Blocking Googlebot?
URL Inspection covers one page. If a whole site or section is missing, check robots.txt next: open yourdomain.com/robots.txt in a browser.
Look for a Disallow: / line under User-agent: Googlebot. That single slash blocks everything beneath it. Watch for staging rules that survived launch. Rules meant to keep a test site out of the index often get carried into production and quietly hide real pages.
Test individual URLs against the file using Search Console’s robots.txt report or a robots.txt tester. Confirm Googlebot is allowed on pages you care about. For proper setup, see our guide to XML Sitemaps & Robots.txt.
One honest caveat: an intentional block is an acceptable reason for a page to be unindexed, such as admin folders or internal search results. Only change what genuinely should be public.
4. Is There an Accidental noindex Tag on the Page?
With robots.txt out of the way, the next likely culprit is a noindex tag. Right-click the page, view the source, and search for “noindex” in a meta robots tag. Also check the HTTP response headers for an X-Robots-Tag saying the same thing.
Then check your theme and SEO plugin defaults, not just one page. A template-level noindex can quietly hide hundreds of pages in one go. In URL Inspection, read the rendered HTML to see what Google saw; your browser view can differ, especially on JavaScript-driven sites. Watch for conflicts: a noindex on the URL Google picked as canonical, or a noindex page still in your sitemap. Mixed signals slow indexing down.
Once the tag is gone, validate the live page and request indexing. A noindex is a deliberate exclusion, so the fix is always removal plus verification.
5. Is WordPress Still Telling Google to Stay Away?
If a page level tag is not the culprit, check WordPress itself. Go to Settings, then Reading, and find the Search engine visibility box. Tick it and WordPress adds a sitewide noindex tag to every page.
This matters most if your site was built on a staging domain, moved hosts, or cloned from another install. The toggle often survives launch, catching businesses that weighed WordPress against custom development and switched in a hurry.
Confirm who adds the tag: WordPress core, your theme, or an SEO plugin with its own global indexing switch. Check the plugin’s titles and meta settings too, since unticking the wrong box leaves the block in place.
Then verify with a site: search and URL Inspection. One checkbox hides the whole site, so it is probably the highest leverage check for smaller sites.
6. Is Your XML Sitemap Missing or Not Submitted?
Next, make sure Google has a map to follow. Confirm a sitemap exists: WordPress SEO plugins create one automatically, but hand built or static sites may have none. Submit it in Search Console’s Sitemaps report and add a Sitemap line to robots.txt so crawlers find it without guessing.
Then check what is listed. A good sitemap holds only canonical, indexable URLs that return a 200 status. Including noindex or redirected URLs just adds noise to your reports.
Use the sitemap as a checklist against your site: search. Pages listed there that never appear in the index are your real problem pages.
Keep expectations honest: a sitemap is a hint about what exists, not a command to index it. Submission alone guarantees nothing.
7. Are Redirects, Broken Links, or 404s Getting in the Way?
Sitemaps tell Google what should exist. Redirects and 404s decide whether it can actually reach those pages. Trace redirect chains: an A to B to C hop wastes crawl effort and can end in a loop Google cannot follow, leaving your final page unindexed. Next, test key pages. Anything returning a 404 cannot be indexed, so 301 it to the closest live equivalent. Then audit internal links, especially after a redesign, a domain move, or an http to https switch, since old URLs often linger in menus and old posts. Search Console’s Pages report surfaces 404s and soft 404s in bulk. Prioritize by traffic and business value rather than fixing every one. And remember: if you deleted a page on purpose with no replacement, a 404 is a perfectly acceptable outcome. Next up: canonical tags.
8. Are Canonical Tags Pointing to the Wrong URL?
If redirects and 404s look fine, the next suspect is the canonical tag. A canonical tag tells Google which version of a page is the one to index. If yours points elsewhere, your page can be dropped in favour of that other URL.
Common duplicate sources: http vs https, www vs non-www, trailing slash variants, paginated archives, filtered category pages. In URL Inspection, compare the canonical Google selected with the one you declared. A mismatch means Google disagrees and is acting on its own. Keep one canonical version per page and 301 the rest; Google’s guidance is clear duplicate URLs should not be indexed. Don’t panic over excluded variants: duplicate URLs being left out is expected and healthy, provided your preferred version is in.
9. Is Your Firewall or Security Plugin Blocking Google?
If your canonicals look right but a page still won’t index, check your security layer. Firewalls, security plugins, and CDN bot protection sometimes treat Googlebot like a suspicious visitor and block its requests.
Watch for the clues: crawl errors in Search Console, a URL stuck on “not indexed,” or a failed live test in URL Inspection, even though the page loads fine in your own browser. Then check server logs for Googlebot visits; genuine traffic from Google’s published IP ranges should appear regularly on a healthy site. Also review CDN settings for aggressive rate limiting, country blocks, or challenge pages that quietly throttle crawling.
The fix: allow Googlebot and verified bot traffic in your firewall, retest with the URL Inspection live test, then monitor the Pages report over the next few days.
10. Any Manual Action or Security Issue in Search Console?
Your firewall looks clean? Great. Next, open the Security Issues and Manual Actions reports in Search Console. Anything unresolved there can quietly pull individual pages, or your entire site, out of Google results.
Manual actions come from a human reviewer, and Google names the violation, usually unnatural links or thin, low value content. علامات التحذير: متى تبتعد عن مزود SEO في دبي؟ is worth reading if someone built those links for you.
Security issues deserve the same urgency. Hacked content, injected spam, or malware warnings suppress pages while damaging visitor trust.
Fix the underlying cause, not the symptom. Then submit a reconsideration request and document exactly what you changed.
Finally, keep them separate: a manual action is a penalty, an indexing error is a technical block. Different problems, different fixes.
11. Is the Page Simply New or Recently Published?
If Search Console shows no manual action, the page may simply be too new. New pages aren’t indexed instantly. Google crawls and indexes on its own schedule, and timing varies by site, page, and demand. Brand new sites have no history or trust signals yet, so Google needs time and evidence before it treats your pages as worth including.
Give yours a head start: request indexing in URL Inspection, submit an updated sitemap, and link to the page from content Google already crawls. If you see “crawled, currently not indexed,” Google found the page but chose to leave it out. That usually points to content quality, intent match, or weak internal linking, not a technical block. So don’t refresh every hour. Recheck with site:exact-url and URL Inspection now and then. No source supports promising a specific indexing timeline.
12. Big Site Wide Blockers: SSL, Downtime, and DNS
If the page isn’t new, something bigger may hide your whole site.
Check HTTPS and SSL first. An expired certificate, a broken chain, or mixed content warnings can stop Google from crawling or shake its trust in your site.
Then review uptime and server logs for 5xx errors. Repeated server errors during a crawl make Google slow down or back off entirely.
Verify DNS next. A misconfigured record, a lapsed renewal, or a recent nameserver change can knock the site offline for crawlers even when it loads fine for you locally.
Check regional or country blocks in your CDN or firewall too. A rule meant for one market can accidentally block the locations Googlebot crawls from.
Finally, rule out the boring stuff: open a fresh browser session, clear your cache, and confirm the problem affects real users before blaming Google.
Conclusion: Your Action Plan to Get Back Into Google
So your site resolves and your certificate is valid, yet Googlebot still stays away? Work in order. Fix access first. Robots.txt blocks, firewall rules, SSL errors and DNS problems stop everything else from mattering, so clear them before page level settings. Then confirm no accidental noindex tags, no WordPress search engine visibility toggle left on, and no canonical tag pointing at the wrong URL. Then submit a clean XML sitemap, request indexing for key pages, and link internally from pages Google already knows.
Verify every fix. Run a site: search, use URL Inspection’s live test, and watch the Pages report over the next few days. Under 500 pages? Google’s guidance suggests skipping that report and using site: searches instead, which is faster for small sites.
Still stuck? An SEO specialist can audit crawl access, indexing and on page signals in one pass and hand you a prioritised fix list. Kiampi Daniel works on exactly this kind of search visibility troubleshooting.
