A new site with few Google clicks does not have one problem called “SEO not working.” Slow indexing means Google has not yet selected some URLs for its index; no ranking means indexed pages have little relevant search visibility; no clicks means you must first establish whether those pages have impressions. Solve these in that order, using your own Search Console property rather than invented indexing or click-through benchmarks.
Set up a baseline before deciding what to fix
Verify a Search Console property that covers the live site, and note your preferred HTTPS host. Make an inventory of the homepage, core service or product pages, category/topic pages and representative articles. For each, record its final URL, HTTP response, robots status, declared canonical, sitemap inclusion, internal-link entry and the Page indexing status. Search Console's URL Inspection report gives the last indexed/crawled view; its live test checks access now but does not predict selection or quality. Google: URL Inspection tool.
Do not combine ten URLs into one percentage and conclude the entire site is “suppressed.” A privacy policy, a parameter variant and a core service page do not have equal search intent. Start with pages meant to answer real searches. If a new site has no search impressions yet, that does not prove all important URLs are unindexed. Conversely, seeing a sitemap entry does not prove a page is indexed.
| Symptom | Evidence to look for | Work to prioritize |
|---|---|---|
| Slow indexing | URL Inspection: unknown, discovered, crawled, excluded or alternate canonical | Discovery links, server/robots/noindex, duplicate selection and page quality. |
| No rankings or impressions | Indexed landing pages with few relevant queries in Performance | Topic choice, page intent, complete answers, relevant internal context. |
| Impressions but few clicks | Performance filtered to page, query, country and device | Actual search appearance, title relevance and the page's promised answer. |
Slow indexing: make important pages discoverable and indexable
Give Google a clean route through the site
A new site often has few incoming links. Link to important pages from navigation, an appropriate category or topic hub, and relevant passages within related pages. A crawlable HTML anchor is more reliable than a clickable card implemented only with a JavaScript event. Do not hide the only link to a service page behind a form, an authenticated area or an infinite-scroll state that lacks accessible pagination. Google's sitemaps guide says internal linking can allow discovery of most important pages and that a sitemap is particularly helpful for new sites with few external links; it does not guarantee indexing. Google: Learn about sitemaps.
Create or verify an XML sitemap of preferred, final URLs. If a CMS generates one already, inspect its contents before adding a second plugin. Submit the sitemap in Search Console, then check whether Google can fetch it. URLs within it should align with final redirects and canonical choices; <lastmod> should reflect genuine meaningful changes, not an automatic daily freshness claim. Google ignores sitemap <priority> and <changefreq>. Google: Build and submit a sitemap.
Test actual responses, not just plugin settings
For each key landing page, check the final public response and rendered content. A 200 is necessary for ordinary HTML indexing consideration but does not guarantee inclusion; a 200 template displaying “not found” can be treated as a soft 404. A 301 to the correct canonical is different from a redirect loop or an unrelated homepage redirect. Persistent 5xx or 429 responses can slow crawling. Google: HTTP status codes and crawlers.
Check robots.txt, HTML robots meta and X-Robots-Tag separately. A testing-site Disallow: / left in production prevents crawling; a stray noindex on accessible pages prevents indexing. Do not combine a robots block with a noindex and expect Google to read the latter. Google: noindex requirements.
Confirm that canonical tags point to the intended public URL and that equivalent HTTP/HTTPS, www/non-www, parameter and trailing-slash variants do not contradict each other. If you run language versions, do not point the English page's canonical at the Chinese version merely because both discuss the same topic; Google recommends a canonical in the same language for an hreflang cluster when available. Google may choose a canonical other than the one declared, so compare the indexed report's two canonical fields. Google: canonical URL methods.
Respond to the actual Search Console state
“Discovered – currently not indexed” calls for checking discovery and crawl conditions; “Crawled – currently not indexed” calls for checking what Google fetched and whether the content is distinctive. “Duplicate, Google chose different canonical” is not a failure to submit; investigate overlapping pages and contradictory signals. A valid live URL test proves only that the live inspection crawler could access it, not that Google will index it. Google: URL Inspection states and limitations.
After correcting a small number of important pages, request indexing through URL Inspection; for many URLs use the sitemap. Multiple requests for the same unchanged URL do not speed the crawl, and submission does not ensure inclusion. Google: Ask Google to recrawl. The Indexing API is restricted to JobPosting or BroadcastEvent embedded in VideoObject; it is not a bulk-submit service for a new company's blog. Google: Using the Indexing API.
Indexed but not ranking: match a useful page to a real query
Once a page is indexed, inspect its Search Console Performance queries and manually look at the result types for its target question in the intended country and language. Is the query asking for a procedure, a comparison, a definition, an official tool or a provider? A new company's sales page will not necessarily satisfy a troubleshooting query just because it repeats the same keyword. The aim is not a prescribed keyword difficulty threshold; it is to give the reader a complete answer that competes on usefulness.
Build the essential pages before multiplying blog posts
Start with a coherent set: a homepage saying what the business does, service/product pages with scope and audience, topic pages that organize related material, and articles answering specific pre-purchase or operational questions. A manufacturing supplier might need a page with specifications and procurement constraints before twenty near-identical posts about “best material.” A software company may need a setup guide that includes actual steps and limitations, not generic benefits. These are editorial examples, not invented customer results.
For each target page, compare the title's promise to the visible text. A “setup guide” should specify prerequisites, sequence, failure modes and what successful completion looks like. A “pricing comparison” should explain units, scope and exclusions. Add original documentation, legitimate screenshots or examples when they exist; do not claim experiments, rankings or customer outcomes without records. Google asks whether a page adds substantial value over other search results, is trustworthy and leaves readers able to achieve their goal. It has no preferred word count. Google: people-first content guidance.
Use internal context, not a fixed link quota
Link the article to the relevant service page where a reader needs the practical next step; link the service page back to an explanation if a technical objection needs detail. Use descriptive link text rather than a repeated exact-match anchor. If multiple new pages compete for the same question, decide whether they should be consolidated or differentiated; splitting one answer into many thin pages does not create more evidence or broader expertise. Google encourages links that can be crawled and understood. Google: crawlable links.
Legitimate mentions and relevant external references may help people and crawlers discover the new site, but “purchase a set number of links to reach page one” is not a measurable promise. Do not treat a third-party authority score, social share count or schema validator pass as Google's ranking formula. If the site needs systematic help connecting technical accessibility, content and commercial pages, see the Google SEO service overview; a service description is not evidence that any given page will rank.
Impressions but no clicks: inspect the result a searcher actually sees
Filter Performance by one landing page, then by relevant queries, target country, device and date range. Ask whether impressions are for the intended topic or a different one; whether the ranking position makes a click likely in that particular result; and whether the displayed title matches what the page offers. Aggregate CTR across branded and generic queries, countries and search appearances is an unreliable pass/fail benchmark. Google's Search Console Performance reporting can separate these dimensions; its data is not the same as your own analytics sessions. Google: Performance report.
Rewrite a vague or overpromising title so it says what the page actually solves; align the main visible heading and opening answer. Check the search result manually because Google may generate its title link from page text, headings or other sources, and may generate a snippet from page content rather than the meta description. A description should summarize the genuine answer, not promise “100% indexing” or repeat keywords. Google: title links and Google: snippets.
Before changing the title, consider a mismatch: a service page receiving impressions for “free template” queries may need a separate, genuinely useful resource rather than a more clickbait service headline. If the page has virtually no relevant impressions, work on intent and usefulness first; CTR optimization cannot create a meaningful search appearance out of no visibility. If the page has impressions and clicks but no leads, inspect on-page clarity and business relevance, not indexing.
A practical launch review with no mythical deadline
- At launch: confirm HTTPS and preferred host, inspect key pages' final responses, robots/noindex/canonical, mobile content, sitemap and internal navigation. Record any sitewide technical problem as a separate incident.
- When new pages are published: place each in a relevant user-facing pathway, verify its full content is publicly available, and use URL Inspection for selected high-value pages if needed. Keep the sitemap current without falsifying
<lastmod>. - As Search Console data accumulates: distinguish discovery, crawl and canonical issues from low impressions, then from low clicks. Review representative queries and competing result formats in the intended market before rewriting.
- After substantive changes: log exactly what changed and compare the indexed crawl date to the live version. Reassess pages with the same intent; do not publish another near-duplicate solely because the first page did not rank.
There is no fixed “sandbox” clock, guaranteed indexed-in-a-week rate or universal CTR target for a new site. Google says crawling can vary and requesting a crawl does not guarantee inclusion. Google: recrawl requests and limits. For a deeper article-level path, use the unindexed article troubleshooting guide. If an indexed page has impressions but few clicks, compare its queries, title and actual result appearance using Search Console's Performance report instead of applying an arbitrary CTR threshold.