Google Search Console: What to Check in the First 90 Days of a New Website

A new website rarely produces a clean SEO story in its first few weeks. Pages are still being discovered, impressions are sparse and one search can make a chart jump. Google Search Console is most useful during this period when you use it to check whether the site can be found, establish a baseline and identify the next sensible improvement—not to demand a traffic forecast from a tiny sample.

First: confirm that the important pages can be found

Set up the correct Search Console property and submit the sitemap. Use URL Inspection on the homepage and a few important pages to see whether Google has discovered them and whether any indexing issue needs attention. A submitted sitemap is a discovery signal, not a guarantee that every URL will be indexed.

Check that the pages you want indexed return successfully, have a self-consistent canonical URL and are linked from relevant parts of the site. If a page is intentionally private, duplicated or temporary, do not treat its absence from search as a failure. Focus first on the pages that should represent the site.

Weeks one to four: create a baseline, not a verdict

Record the dates covered, clicks, impressions, average position and the pages that appear in the report. Early numbers may be small or incomplete, so note the sample size and avoid overreacting to a single day's movement. Use the Queries and Pages reports together: a page can appear for unexpected searches, and one query can lead to several relevant pages.

Make sure the landing page answers the searcher's question clearly. If the title promises a specific guide but the page opens with a generic studio pitch, improve the match before producing more pages. A useful first-month task may simply be clarifying a title, adding internal links or fixing a technical issue.

Weeks five to eight: look for patterns worth investigating

Compare a consistent date range and identify pages that have begun to receive impressions. Inspect the actual queries before changing copy. A low click count can mean the page is new, the query is too broad, the result snippet is unclear, or the searcher wants something different. Position and click-through rate are clues, not diagnoses.

Choose one page and one hypothesis. For example: “The page receives impressions for a specific setup question, but its introduction does not answer that question quickly.” Make a focused edit, record its date and avoid changing several unrelated elements at once. That gives a later comparison some meaning.

Weeks nine to twelve: review the change and decide what comes next

Return to the edited page after enough time has passed for the relevant queries to accumulate. Compare the same page and a comparable period, while remembering that seasonality, ranking changes and small sample sizes can distort the result. Keep the change if it improves usefulness or visibility; revise the hypothesis if the evidence points elsewhere.

Prioritize work with a simple queue: technical blockers first, then pages with clear search intent and a realistic path to improvement, then new content where the site has a genuine coverage gap. Do not create near-identical pages just to increase URL count. A small group of well-linked pages is easier to maintain and more useful to readers.

For a lightweight review, Rank for Mac helps turn Search Console data into a shortlist of pages and follow-up actions. You can also start with the free Search Console opportunity finder before choosing a paid workflow.

At day 90, the win is a reliable baseline and a clearer next decision. Search Console is a measurement tool, not a promise that a new site will rank on a fixed schedule.