Why Has My Website Disappeared from Google?
A website can seem to vanish because of deindexing, ranking changes, technical faults, migrations or reporting differences. Confirm the symptom before changing the site.
Part of our guide: Website SEO: A Beginner’s Guide for Small Businesses
A website may appear to disappear from Google because its pages were removed from the index, rankings fell for particular searches, URLs changed, technical controls blocked crawling, or the way you searched changed. First inspect the exact URL in Google Search Console and compare search-performance dates with website releases. Do not rebuild or rewrite everything until you know which symptom occurred.
If the homepage is still indexed but enquiries fell, the problem is different from an entire domain returning “URL is not on Google”.
Confirm what “disappeared” means
Write down the affected URL, query, location, device and date first noticed. Check whether the concern is:
- the exact page is no longer indexed;
- the page remains indexed but ranks lower;
- a search-result title or description changed;
- traffic fell while rankings appear stable;
- only the business profile or map result is missing;
- analytics stopped recording visits.
These require different investigations.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Inspect the exact URL in Search Console
Paste the full URL into URL Inspection. Check the overall indexing status, last crawl, crawl permission, page fetch result, user-declared canonical and Google-selected canonical.
Run a live test if the indexed view shows an old problem. A successful live test suggests the current page is accessible, but Google still needs to recrawl and process it. Google’s URL Inspection documentation explains the difference.
Use our guide to checking which pages Google has indexed when several sections may be affected.
Separate indexing from ranking
An indexed page can move lower for a query because competitors, intent, content, location and many other signals changed. Search Console’s Performance report can show impressions, clicks, queries, pages and average positions over time.
Compare equivalent periods and annotate major campaigns, seasonality and releases. A fall in clicks with stable impressions may reflect result appearance or demand, while a simultaneous loss of impressions across many pages suggests a wider visibility change.
Average position is an aggregate, not a fixed rank. Segment by query, page, country and device before drawing conclusions.
Check recent website changes
Ask for a release log covering the date of decline. Common causes include:
- a redesign or platform migration;
- changed URL paths without redirects;
- a global
noindexsetting; - robots rules copied from staging;
- canonicals pointing to another domain;
- deleted content or navigation links;
- server errors or DNS changes;
- rewritten titles and content;
- JavaScript rendering failures.
Revert or fix a clearly harmful technical release carefully. Avoid restoring an entire old site blindly when one configuration error is responsible.
Look for accidental noindex
Inspect page-level meta tags and HTTP response headers. A global setting can remove many pages from eligibility after Google recrawls them.
Remove accidental noindex, test the live page and request indexing for priority URLs. Keep the instruction on pages intentionally excluded from public search.
If pages are blocked in robots.txt, Google may be unable to see their updated indexing instruction. Coordinate crawl access and indexing controls rather than changing one in isolation.
Review redirects and URL changes
A redesign often changes folders, filenames or domains. Each valuable old URL should redirect permanently to the closest relevant new page. Redirecting everything to the homepage loses context and may be treated as a soft error.
Check redirect chains, loops and destinations. Update internal links and sitemap entries to point directly to final canonical URLs.
Google’s site-move guidance warns that significant moves can produce temporary ranking fluctuations while old and new URLs are recrawled. Our guide to redesigning without losing Google rankings provides a practical migration process.
Check canonical changes
Google may exclude a page when it considers another URL the canonical version. This can happen after templates start pointing every canonical to the homepage, a staging site or a similar product page.
Compare the user-declared and Google-selected canonical in URL Inspection. Align redirects, internal links, sitemap entries and canonical annotations. Do not use canonical tags to conceal genuinely different pages.
Check server, DNS and security incidents
If Google repeatedly encountered 5xx errors, timeouts or DNS failures, crawling and visibility can suffer. Review hosting uptime and server logs around the decline.
Security compromises can inject spam, redirect visitors or trigger browser and search warnings. Check Search Console’s Security Issues report and inspect the site from clean devices. Use qualified security help before restoring compromised files.
Temporary maintenance should return an appropriate temporary status rather than a permanent removal signal. Long outages require clear communication and monitoring.
Review manual actions
Search Console has a Manual Actions report. A manual action means a human reviewer determined that pages did not comply with Google’s spam policies. The report identifies the type and affected scope.
Fix the underlying issue thoroughly and submit a reconsideration request through the documented process. Do not hire someone promising to conceal the same practice or manufacture a quick recovery.
A visibility loss without a manual action is not proof of an algorithmic penalty. Most technical and competitive changes do not produce a manual-action message.
Check removals and legal requests
Search Console’s Removals tool can temporarily hide URLs from Google Search. Review whether an authorised user submitted a request. Also check whether the URL now returns removal signals or was deleted from the site.
Legal removals and safe-search filtering are separate processes. If Search Console or Google’s transparency tools identify one, follow the relevant appeal or correction route rather than changing unrelated SEO settings.
Compare the sitemap and internal links
A page removed from navigation but left in a sitemap has weaker structural support for users and crawlers. A page removed from both can become difficult to rediscover.
Restore meaningful links from relevant hubs and articles. Keep only canonical, indexable URLs in the sitemap. Ensure the homepage and key category pages still lead to the services the business actually offers.
Also audit the XML sitemap so it contains the new canonical destinations rather than obsolete routes.
Review content changes calmly
A redesign can shorten a useful page, remove evidence, merge distinct services or change the search intent it addresses. Compare the old and new content using backups or archives you are authorised to access.
Restore information that genuinely helps the customer, not every repeated phrase from the previous page. Preserve important titles, headings and internal-link context where they remain accurate.
Search visibility can also change because competitors publish stronger information or demand shifts. Technical repair alone cannot reverse every ranking movement.
Consider broad search-system changes carefully
Google makes frequent changes, and industry monitoring may report broader updates. Use official Google Search Status information and your own segmented evidence. A date correlation does not prove a specific cause.
Avoid emergency tactics such as deleting large sections, buying links or rewriting all pages at once. Those changes destroy the baseline needed to understand recovery.
Make an incident timeline
Create one table containing:
- date and time;
- affected pages or query group;
- Search Console evidence;
- analytics evidence;
- website release or infrastructure event;
- observed technical change;
- action taken;
- next review date.
This prevents several suppliers from making conflicting changes. Save exports before filters and retention periods alter what you can see.
Prioritise by scope and impact
An entire domain blocked by noindex is urgent. A single obsolete article losing impressions may not be. Fix access, indexing controls, response errors and broken migrations before adjusting wording for marginal ranking changes.
After a fix, validate a small sample of affected URLs and request indexing for the most important. Allow time for recrawling before judging the outcome.
A first-hour checklist
- Confirm the exact URL and search symptom.
- Inspect the URL in Search Console.
- Check Performance data by page and query.
- Review releases and hosting incidents.
- Check robots,
noindex, canonical and status codes. - Test redirects from former URLs.
- Review Manual Actions and Security Issues.
- Preserve evidence before making changes.
- Assign one person to coordinate the response.
- Fix the confirmed cause and schedule validation.
When a redesign is involved
Read does redesigning a website affect SEO? to understand which changes create risk. A sound redesign can improve technical quality, content and usability, but it needs a URL inventory, redirect map and pre-launch checks.
Google must recrawl changed URLs, so some movement may be temporary. Missing redirects, wrong canonicals and staging blocks are not normal fluctuation and should be corrected promptly.
Frequently asked questions
Has Google penalised my website?
Not necessarily. Check Manual Actions, Security Issues, indexing controls, migrations and query-level performance. A decline alone does not identify a penalty.
Can my developer get the old rankings back immediately?
No one can guarantee rankings or processing speed. A developer can repair technical faults and redirects; Google still recrawls and reassesses the pages.
Should I submit every missing URL again?
No. Fix the cause, submit a sitemap and request indexing for a small number of important pages. Repeated unchanged requests do not accelerate crawling.
Could analytics be wrong?
Yes. Consent changes, broken tags and reporting filters can create an apparent traffic loss. Compare Search Console and server evidence before concluding that search visibility disappeared.
Diagnose before reacting
A website that vanishes from search needs evidence-led incident handling. Confirm whether the issue is indexing, ranking, reporting or local visibility; then trace the timing to technical and editorial changes.
Afterworks plans redirects and search safeguards when replacing an existing site. Explore our website rebuild service or contact us if a migration or redesign has disrupted visibility.
