A website that is not ranking on Google may have an indexing problem, weak relevance for the searches it targets, or a loss of visibility it previously had. Falling clicks can also come from changes in demand or the results page, even when rankings appear fairly steady.
Those situations need different responses. Start with one important URL and the search it should answer. Establish what Google has indexed, what the page actually appears for, and when the problem began. Then make a change that addresses the evidence.
Publishing more articles, buying links, or replacing an SEO plugin before doing those checks can leave the original problem untouched.
First, identify which problem you actually have
“My website is not ranking” describes several different situations. Use the closest match below to decide where to begin.
| What you are seeing | First check | What you need to establish |
|---|---|---|
| A particular page cannot be found | Inspect its exact URL in Search Console. | Whether Google has indexed it, excluded it, or selected another URL as canonical. |
| The page is indexed but gets little relevant visibility | Review its queries and the results for the intended search. | Whether the page answers the right need and offers a credible alternative to current results. |
| A page that previously performed well has declined | Compare the affected period, pages, and recent website changes. | Whether the loss is isolated, widespread, technical, or related to changed search demand or competition. |
| Clicks have fallen while visibility appears similar | Compare queries, CTR, devices, and search result features. | Whether people are seeing a different mix of results or choosing your listing less often. |
| Search visits continue but enquiries have fallen | Test the enquiry journey and measurement. | Whether the problem happens after the visit rather than in search rankings. |
A search from your own phone is useful context, but it is not a complete performance report. Location, device, query wording, and the results available at that moment can affect what you see.
Build a baseline before changing the website
Write down the affected URL, the business need it serves, the searches you expected, and when you first noticed the problem. Note any redesign, domain change, content replacement, plugin change, or hosting move near that date.
In Search Console’s Search results performance report, start with Web search and comparable date ranges. A recent complete 28-day period against the previous 28 days can be a useful starting point. Seasonal businesses should also examine the equivalent period in the previous year when available.
- Look at the overall trend. Establish whether the change affects the whole property or just a few pages.
- Select the affected page. Review its queries instead of relying on site-wide totals.
- Separate your business name from other searches. A page may appear for branded queries while remaining largely absent for services customers need.
- Check the relevant country and device. A change in overseas traffic can distort the picture for a local business.
- Record what changed. Compare impressions, clicks, CTR, and position together, then save the filtered view or export.
Google’s performance report documentation explains the report and its measures. An average position combines appearances across searches; it is not a single fixed rank for your website. Small totals also need care: a few impressions are too little evidence for a confident trend.
If the only decline is in website analytics, check whether tracking or consent settings changed. Search Console clicks and analytics sessions measure different events and should not be expected to match exactly. Google’s guidance on using the two data sources together explains those differences.
If the page is not indexed, identify the exclusion first
Open URL Inspection and enter the complete page URL. Read the indexing result, last crawl information, and Google-selected canonical. A canonical is the URL Google treats as the main version among similar pages.
If you recently changed the page, run Test live URL to check current access. The indexed result describes what Google has processed; the live test checks the page as it is now. A successful live test does not guarantee indexing or predict Google’s canonical choice. See Google’s URL Inspection guidance.
A site: search can offer clues, but Google says it is not an exhaustive list of indexed URLs. Use the inspection result to investigate a missing page.
| Finding | Next decision |
|---|---|
| An unexpected noindex directive or crawl/access block | Confirm the page should be public and searchable, then identify the setting or rule responsible. |
| A redirect or alternate canonical | Inspect the destination. The old URL may be excluded correctly; investigate if Google chose an unintended version. |
| Discovered or crawled, but currently not indexed | Review the reported state, access, internal discovery, duplication, and usefulness. The label alone does not identify one universal cause. |
| A missing page, server failure, or soft 404 | Check whether the content should exist and whether the server delivers the expected page. |
The Page indexing report helps determine whether the same issue affects other URLs. Not every excluded URL needs fixing: account pages, duplicates, and retired URLs can be intentionally absent.
For implementation, use our technical SEO audit and fix checklist. It covers robots directives, canonicals, rendering, and redirects in detail. After correcting a confirmed problem, verify the change and request indexing where appropriate. Repeated submission is not a substitute for fixing the underlying condition.
If the page is indexed but ranks poorly, compare the search need
Indexing makes a page available for consideration. It does not establish that the page is the best result for every related query. Investigate the specific searches that matter to the business.
Does the page match what the searcher is trying to do?
Review several relevant results for the intended query. Are people being shown service providers, product categories, comparisons, tutorials, or local listings? Note the pattern without treating one results page as a permanent rule.
An article explaining how a service works may not satisfy someone trying to hire a provider. A sales page may not answer a person looking for troubleshooting instructions. Decide whether you should improve the existing page, target a different need, or create a genuinely distinct page.
Use our keyword research guide to investigate demand and map needs to pages. Here, the diagnostic question is whether the current page has been assigned the right job.
Does the page give someone enough evidence to choose it?
Read the page as a prospective customer. Can you understand the actual service, who it suits, what is included, and what happens next? For an informational page, can you act on the answer or verify its claims?
Identify a concrete gap. That might be missing project evidence, an unexplained limitation, outdated specifications, or instructions that stop just before the difficult step. “Make the article longer” is not a diagnosis. Google’s helpful content guidance focuses on usefulness and original value rather than a preferred word count.
Our on-page optimization checklist covers the editing work once the gap is clear.
Is another page serving the same purpose?
Filter a relevant query in Search Console and examine the Pages view over comparable periods. Look at the URLs that appear and what each one offers. Two pages appearing for a query is not, by itself, proof that they harm each other.
Concern is more justified when near-identical pages serve the same need, important links point to inconsistent destinations, or an unsuitable page repeatedly appears where the intended page should. Compare content and purpose before deciding what to change.
Keep pages that answer distinct questions and connect them with useful links. When two pages are genuinely redundant, consolidate their useful material into the better destination and plan any redirect deliberately. Do not delete a helpful guide just because it mentions the same service as your main sales page.
Is the competitive gap broader than the wording?
Check whether the page is easy to reach from relevant parts of your own website. Then consider whether competing businesses have stronger evidence, established recognition, or useful external references that your site lacks.
A low backlink total does not prove that Google distrusts the website, and there is no universal number of links needed to rank. If relevant external coverage is a realistic gap, our link building guide explains how to assess opportunities. Buying a package of links before resolving a mismatch in page purpose is unlikely to address that mismatch.
If rankings dropped, investigate what changed and where
Start with the date and scope of the loss. One URL disappearing after an address change points to a different investigation from many unchanged pages declining across several topics.
- After a redesign or move: compare old and new URLs, important content, indexing settings, redirects, and internal links.
- Across one section: check shared templates, navigation changes, and whether content or settings changed together.
- Across many pages: check availability, Search Console notices, demand, and Google’s published update information.
- In one report only: investigate filters, tracking changes, or a documented reporting issue before treating it as lost visibility.
Google’s traffic drop guidance covers several possible causes, including technical problems, algorithm changes, seasonality, and changing interests. A decline can have more than one contributor.
Review Search Console’s Manual actions and Security issues reports when a sudden loss suggests a serious problem. A manual action is a specific finding reported by Google; an ordinary ranking decline does not establish that one occurred.
If the dates overlap a core update, check whether the rollout has finished. Google recommends waiting at least a full week after completion before comparing performance with the period before the update. Follow its core update guidance and assess affected pages carefully rather than making a series of unsupported changes.
For unusual reporting patterns, check Google’s Search Console data anomalies. A logging problem can change a chart without changing what users saw.
If clicks dropped but rankings look stable, inspect the results page
A stable average position does not guarantee a stable number of clicks. The mix of queries may have changed, fewer people may be searching, your title may be less compelling for those searches, or the visible results may offer other ways to get an answer.
Compare the same page and relevant query groups where the data allows. Then inspect representative results from the market you serve. Look at ads, local results, shopping or video features, competing listings, and AI answers.
The following figures are hypothetical and illustrate a diagnosis, not a client result:
| Measure | Earlier period | Later period |
|---|---|---|
| Impressions | 5,000 | 4,800 |
| Clicks | 200 | 96 |
| CTR | 4% | 2% |
| Average position | 6.2 | 6.4 |
Clicks fell much more than impressions. That makes query mix and click behaviour worth investigating. It does not prove that an AI answer caused the decline, or that every individual query held its position.
How AI Overviews and AI Mode fit into the investigation
An AI answer may satisfy part of a search without a visit, while a supporting link can introduce a reader to a source. Assess the actual result and available data before deciding how these features affect a particular page.
Google introduced dedicated generative AI reporting in 2026. The Generative AI performance report for Search shows impressions for links appearing in AI Overviews and AI Mode, with page, country, device, and date breakdowns. Use it to investigate whether the affected pages receive visibility in those features.
The documented report focuses on impressions. It does not give you an isolated AI click-through rate or prove why ordinary search clicks changed. Its data is included in the broader Web performance data, so do not add the totals together as though they were separate audiences. A missing report or sparse data is not sufficient evidence of an AI visibility penalty.
If the concern is specifically absence from Google’s AI features, check Settings → Search generative AI. Google’s Search generative AI control can exclude content from those features without changing inclusion or ranking in other parts of Search. Check the effective setting, including any inherited choice, before assuming that the content itself is the problem.
For improvements, focus on accurate answers, useful original details, and content people can verify. Google’s AI search guidance says there is no requirement for special AI text files or a particular page length. Adding an FAQ solely to pursue an AI citation does not resolve missing evidence or an unclear answer.
If the page uses AI-written content, examine the result
Using AI does not, on its own, establish why a page ranks poorly. Google’s guidance on generative AI content recognises uses such as research and structure, while warning about producing many pages without added value.
Compare the published page with what the business can actually substantiate. Look for invented services, incorrect locations, outdated product details, unsupported statistics, or paragraphs that could describe almost any competitor.
A useful correction is specific. Replace a generic service description with the actual scope and limitations. Add an authorised project example where it answers a customer’s question. Remove a claim you cannot verify. If several articles repeat one answer, review whether they need separate pages.
Changing a few words to sound less automated leaves those problems in place. The question is what information the reader gains and whether it is dependable.
If the problem is local visibility or lost enquiries, change the investigation
A website appearing in organic results and a business appearing in Google Maps are different outcomes. If the missing result is a map listing, check that surface separately. Our Google Local 3-Pack guide covers that branch of the work. Repeating a city name throughout an article is not a substitute for investigating the local listing.
If relevant search visitors still arrive but enquiries decline, test the mobile page, contact links, forms, confirmation messages, and delivery of submissions. Check what changed in the offer and whether measurement still records completed actions.
Performance and usability deserve attention when users encounter a real problem. Google’s page experience guidance also makes clear that good Core Web Vitals alone do not guarantee high rankings. A speed score should not become the explanation for every search or conversion problem.
Turn the diagnosis into a change you can verify
Record the observation, the explanation you are testing, the change, and the evidence needed to assess it. Keep confirmed faults separate from ideas that still need investigation.
| Evidence | Focused action | Verification |
|---|---|---|
| An intended service page has an accidental noindex directive. | Correct the setting responsible. | Check the live page, then monitor the processed indexing result. |
| A tutorial receives visibility for a service enquiry while the service page is vague. | Clarify the service page and the route from the tutorial to it. | Review relevant queries and landing pages over time. |
| A previously useful URL now redirects to an unrelated page. | Restore the expected content or choose an equivalent destination. | Test the redirect and destination, then monitor discovery and performance. |
| Clicks fall with no comparable loss of impressions. | Investigate query mix, listing presentation, demand, and result features. | Compare matching segments and document what the evidence supports. |
| Visits continue but the contact form fails. | Repair and test the full submission journey. | Confirm receipt and reliable recording of completed enquiries. |
Fix urgent access and functionality failures promptly. For other work, avoid changing the page’s purpose, URL, content, and linking strategy all at once without a clear reason. Otherwise, it becomes harder to tell what helped.
Implementation can be verified before a ranking outcome appears. A removed noindex directive is a checkable correction; the eventual position of the page remains uncertain. Allow time for processing and enough observations to evaluate the result. There is no universal recovery deadline.
If you need help, bring the affected URLs, the date the problem began, recent change records, and relevant Search Console exports. Maple Web Design’s SEO services explain how to arrange a review and plan the work around the problem you actually have.
