Why Is My Website Not Ranking? A Diagnostic Order

"Why is my website not ranking" has about eight common answers, and they are not equally likely. Working through them in the wrong order wastes weeks. This is the order that rules out the most in the least time, with the check for each.

1. Is it indexed at all?

Search site:yourdomain.com in Google. If you see nothing, or far fewer results than you have pages, nothing else matters until this is fixed.

The usual causes: a noindex tag left in from staging, robots.txt blocking the site, the site being too new for Google to have crawled it, or pages sitting behind authentication. Search Console's Page Indexing report names the reason per URL, which turns this from guesswork into a list.

Most common single cause of "not ranking" on a new site. Check it first, every time.

2. Is the specific page indexed?

Site-level indexing can be fine while the page you care about is excluded. Use Search Console's URL Inspection on that exact URL. The verdicts that matter:

• "Excluded by noindex tag" — a template or CMS setting. Fixable in minutes.

• "Duplicate, Google chose different canonical" — Google decided another URL is the real version. Usually means you have near-identical pages competing.
• "Crawled, currently not indexed" — Google looked and declined. This is a quality judgement, and the hardest to fix.
• "Discovered, currently not indexed" — Google knows the URL exists but has not prioritised crawling it. Often a crawl budget signal, especially on large sites.

3. Does the page target the query at all?

Read the page as Google would. Is the target query in the title, the H1 and the opening paragraph? A surprising number of pages that "should rank" for a term never actually state it in the places that matter.

4. Does the format match the intent?

Search your target query in an incognito window. Look at the top ten. Are they listicles, product pages, forum threads, documentation?

If the entire first page is listicles and yours is a product page, you are in the wrong race. No amount of on-page work fixes a format mismatch — you either change the format or change the query.

This is the most commonly missed cause among people who have already done the technical basics.

5. Are you competing with yourself?

If two or more of your pages target the same query, Google picks one and often ranks it worse than a single consolidated page would rank. The tell is several of your URLs appearing for the same query across different weeks, or Search Console showing impressions spread across near-identical pages.

Detecting this properly means grouping queries by the page Google routes them to, then looking for queries where that routing is unstable. UtilitySEO does that automatically from Search Console data rather than requiring you to group keywords by hand, which is the part that usually does not get done.

6. Is the site fast enough and does it render?

Run PageSpeed Insights on the page. Below 50 on mobile, performance is plausibly holding you back on competitive queries.

Separately, if the site is React, Vue or another JavaScript framework, check what Google actually sees using URL Inspection's rendered HTML view. If your content is missing from it, you have a rendering problem rather than a ranking problem, and it will not resolve on its own.

7. Has the site been penalised?

Search Console, Manual Actions and Security Issues. Takes ten seconds and either rules out a whole category or changes everything. If there is a manual action, stop the rest of this list and work the reconsideration process.

8. Is the site simply not authoritative enough yet?

If everything above checks out and you still do not rank, this is usually the answer, and it is the least satisfying one. New domains in competitive niches routinely sit at position 40 to 70 on any query with real search volume, while ranking well on long-tail queries nobody searches.

The diagnostic: compare your positions on high-volume versus low-volume queries. If you rank well only where volume is negligible, you are hitting an authority ceiling, not a technical problem. More content will not fix it. Links, brand searches and time will.

The order matters

Steps 1 to 3 take about ten minutes and resolve most cases on newer sites. Step 4 catches the most common non-technical cause. Steps 5 to 7 are quick eliminations. Step 8 is what remains, and it is a different kind of problem requiring a different kind of work.

The mistake almost everyone makes is starting at step 8 — assuming it is an authority problem and publishing more content — when the actual cause is a noindex tag or a format mismatch that would have taken twenty minutes to find.