Find SEO opportunities
in Search Console.

Set a baseline.

Choose the correct Search Console property and a consistent search type. Compare equal-length, complete periods, keeping filters the same. A 28-day comparison includes the same mix of weekdays, but still needs context if a holiday, campaign, or seasonal demand changed.

Search Analytics data can lag by a few days, and query detail is not a complete ledger of every search. Some data is omitted when you request page or query dimensions. Check dates and coverage before interpreting a quiet table as “no interest.” See Google's Search Console API data guidance.

Record the starting clicks and impressions, the pages you will review, and any known site changes. This becomes the reference for your next decision.

Read the change.

The Search Console Performance report measures clicks from Search, appearances in results, click-through rate, and average position. CTR is clicks divided by impressions. Average position summarizes the topmost result for the grouping; it is not a fixed rank that every searcher sees.

These patterns suggest questions, not proven causes. Segment by page or query before deciding that an entire website needs a rewrite.

Pick a page worth improving.

Start where the search intent matters to your audience and you have enough evidence to act. A page already earning relevant impressions may deserve attention before a new article on an unrelated high-volume phrase.

Write a short hypothesis: “People searching for setup steps land on a general overview. Add a clear setup section and link to it from related documentation.” Choose a change you can explain from the evidence, rather than repeating keywords across the page.

Inspect before you edit.

Open the page on a phone. Can a visitor identify what it offers, find the answer, and take the next step? Check inaccurate information, missing explanations, unclear headings, and broken internal links.

For a technical concern, inspect the URL in Search Console and review its reported indexing and canonical status. For a relevance concern, compare the page with the actual intent behind its queries. A competing page is a review candidate, not an automatic instruction to delete or redirect it.

Use a clear, accurate page title. Google can form title links from several page signals, so your title element is an influence rather than an exact display instruction. Read Google's title link guidance. Keep the body useful for visitors; the SEO Starter Guide explains the foundations.

Measure and learn.

Log the page, the change date, the problem you observed, and the outcome you expect. Where practical, make one coherent improvement at a time so the follow-up has a useful explanation.

Review subsequent complete periods after Google has had time to revisit the page and enough data has accumulated. Look at the relevant queries and pages, not just the site total. A before-and-after result is an observation, not proof that your edit caused every change.

Keep improvements that help people even if the ranking effect is unclear. Next week's action might be a technical fix, a better explanation, or no change while you collect more evidence.

A new website needs discovery first.

Verify the property, submit a sitemap of useful public canonical pages, and inspect the homepage. Keep private account and workspace pages out of your indexable content. Check for accidental login requirements or indexing directives on pages you want people to find.

If a page is new or substantially updated, an authorized property owner can request indexing through URL Inspection. A request does not guarantee inclusion or make repeated requests speed up crawling. See Google's recrawl guidance.

Build relevant, original pages that answer real audience questions. Share them where interested people will find them. Indexing is the foundation; useful content, competition, and sustained improvement determine the opportunity to earn visibility. No sitemap or SEO tool guarantees a first-page position.