Most small businesses don’t need another SEO dashboard. They need a short routine that catches problems while there is still time to fix them.

Google Search Console is built for that job. It shows how Google crawls, indexes, and serves your site, along with the searches that produced impressions and clicks. Google says business owners should at least understand the basics, even if a marketer or developer handles the account: Google’s overview of Search Console.

The trouble is that Search Console can become a rabbit hole. A business owner sees hundreds of excluded URLs, a lower average position, or a red Core Web Vitals chart and assumes something is broken. Sometimes it is. Often the number needs context.

This 30-minute weekly triage helps you separate a real business risk from background noise. You are not trying to complete an SEO audit. You are answering three questions: Did anything important break? Did demand change? What is the next useful action?

Before You Start: Pick the Pages That Pay the Bills

Make a short list of your five to ten money pages. These are usually service pages, location pages, product categories, booking pages, quote pages, or a few articles that regularly create qualified leads.

This list keeps the review grounded. A 40% click loss on your main emergency plumbing page matters more than a 100% loss on an old post that received two clicks. Search Console reports can be grouped by page and query, so you can review the URLs tied to revenue instead of treating every URL equally: Google’s Search Console getting-started guide.

Also confirm that you have the right property. A Domain property combines protocols and subdomains, while a URL-prefix property covers only the exact prefix you added. Google’s verification documentation explains those boundaries and the available ownership methods: verify your site ownership in Search Console.

Write down the comparison you will use each week. For most small businesses, the last 28 days compared with the previous 28 days is a useful starting point. Seasonal companies should also compare with the same period last year. The important part is consistency.

Minutes 0-5: Check for Alerts and Serious Site Problems

Start with the Overview page. Look for new messages, security issues, manual actions, or a sudden change in indexed pages.

Do not start by chasing every warning. Start with conditions that can remove pages from search or put visitors at risk. Search Console’s Security Issues report covers signs that a site may have been hacked or may harm visitors, while the Manual Actions report identifies cases where some or all of a site may not appear in Google Search: Google’s guide to Search Console reports.

If either report shows an active problem, stop the routine and escalate it. Take screenshots, record the affected URLs, and contact whoever maintains the site. A manual action or hacked-page warning is not a task to put on next month’s content calendar.

Next, glance at the Page indexing chart. You are looking for a sharp change, not a perfectly clean report. Google attempts to index pages it discovers, and the report includes pages that are not indexed for expected reasons. Redirected URLs, duplicate URLs, and pages intentionally marked noindex can appear outside the indexed total without representing a failure.

The useful question is narrower: did an important page move from indexed to not indexed? If so, use URL Inspection. Google says that tool shows the current index status, lets you test a live URL, and provides details about loaded resources: Google’s URL Inspection overview.

Record the exact reason shown. “Crawled, currently not indexed,” “Blocked by robots.txt,” and “Excluded by noindex” point to different investigations. Do not send your developer a screenshot that only says “Google isn’t indexing pages.” Send the URL, the reported reason, when you first noticed it, and whether the page recently changed.

Minutes 5-15: Find Meaningful Click and Impression Changes

Open the Performance report and set your comparison. Review total clicks and impressions, but do not stop there.

Clicks tell you that someone selected your result. Impressions tell you that a result from your site appeared in Search. Average click-through rate divides clicks by impressions, while average position summarizes the topmost position of your site across impressions. Google documents these definitions and warns that position can be difficult to interpret because results vary by search feature and page: Search Console Performance report metrics.

Now switch to the Pages tab and sort by click difference. Check both the largest losses and gains. For each large change, ask:

  • Is this one of our money pages?
  • Did impressions change, clicks change, or both?
  • Did we change the page, title, offer, hours, pricing, or URL?
  • Is the comparison distorted by a holiday, weather event, promotion, or seasonal demand?

This is one of only two lists you need during the routine. Keep it practical.

An impressions decline can mean fewer people searched for the topic, your visibility fell, or the page stopped appearing for some searches. Stable impressions with fewer clicks may point to a weaker search result, a change in search features, or a mismatch between the page title and what searchers want. Higher impressions with flat clicks may be good news if the page is beginning to appear for more relevant searches, but it deserves a closer look at the Queries tab.

Filter to one affected page, then open Queries. Separate branded searches from non-branded searches. A branded query includes your company or product name. A non-branded query describes the problem or service without naming you. That split is not a built-in business verdict, but it helps explain whether people already knew your name or discovered you while shopping.

Do not overreact to one query. Google omits some queries from tables to protect user privacy, and chart totals may include anonymized query data that does not appear in the table: Google’s explanation of Performance report data limits. Look for clusters of related terms and page-level movement.

Minutes 15-20: Check New and Recently Changed Pages

Make a list of pages published, rewritten, redirected, or removed during the past two weeks. Inspect the important ones individually.

For a new page, confirm that the live test returns a usable page and that Google is allowed to index it. If it is not indexed yet, request indexing once after you have checked the page. Repeated requests do not replace internal links, a working sitemap, or a page worth finding.

Google says properly linked pages can usually be discovered through navigation and internal links. It also says a sitemap can help crawling on larger, newer, or media-heavy sites, although small sites with good internal linking may not need one: Google’s sitemap guidance.

That gives you a better checklist than clicking “Request indexing” every morning. Confirm the page appears in the XML sitemap if it belongs there. Link to it from at least one relevant page that Google already knows. Make sure it is not blocked, redirected, canonicalized somewhere else, or tagged noindex.

Be careful with noindex. Google documents that a robots meta tag can prevent a page from appearing in results, but the crawler must be allowed to access the page to read that instruction: Google’s robots meta tag specification. Blocking a URL in robots.txt while expecting Google to process a noindex tag creates conflicting instructions.

For a redirected page, inspect both the old and new URLs. Confirm visitors land on the correct replacement and that the destination is indexable. A redirect to the homepage may technically work while providing a poor answer to the person who expected a specific service or product.

Minutes 20-25: Review Page Experience Without Chasing a Perfect Score

Open Core Web Vitals and look for a new group of poor URLs, especially if it includes money pages. The report uses real-world usage data, sometimes called field data, rather than only a one-time lab test: Google’s Search Console guide.

Treat this as a diagnostic, not a scoreboard. Google says Core Web Vitals are used by its ranking systems, but a perfect score does not guarantee top rankings. It also says page experience includes more than one or two technical measurements, including secure delivery, mobile display, intrusive interstitials, and whether the main content is easy to identify: Google’s page experience guidance.

If a template-wide problem appears, test a representative service page, blog post, and contact page. Common causes include a newly added chat widget, oversized hero image, consent tool, review widget, or script added through a tag manager. Note what changed before approving a broad rebuild.

Prioritize fixes that help customers as well as search performance. A booking form that jumps while loading, a button that responds late, or a mobile popup that covers the page can cost leads even if rankings do not move.

Minutes 25-30: Choose One Action and Assign It

End the review with one clearly assigned action. If you finish with 37 screenshots and no owner, the routine failed.

Use this format: page, evidence, action, owner, due date, success check.

For example: “Emergency HVAC service page, clicks fell 31% while impressions stayed stable over the last 28 days. Rewrite the title and description to match the 24-hour repair offer. Maria owns it by Friday. Review click-through rate after another 28 days.”

That example does not claim the title caused the decline. It states what the data shows, identifies a reasonable test, and sets a review window.

Other good weekly actions include restoring an accidental noindex, adding internal links to a new service page, correcting a broken redirect, checking a lost query cluster against the page copy, or removing a script that damaged mobile performance.

Avoid vague tasks such as “improve SEO,” “fix Search Console,” or “publish more content.” Nobody can close them, and you cannot measure whether they worked.

When a Change Is Not an Emergency

Search data moves. A local roofer gets different demand after a storm. An accountant sees tax-season patterns. A restaurant may gain branded searches after local press. Search result layouts also change.

Google recommends checking Search Console about once a month or after site changes, rather than feeling obligated to sign in daily. It also sends email when it finds new issues: Google’s Search Console usage guidance. A weekly review is useful for businesses actively publishing, advertising, changing services, or relying heavily on organic leads, but it should remain a short exception-based review.

Escalate when an important page disappears, a security or manual-action alert appears, leads and relevant clicks fall together, or a technical problem affects a group of revenue pages. Keep watching when the movement is small, isolated, seasonal, or limited to low-value URLs.

The goal is not to make every chart green. The goal is to catch lost revenue opportunities early and give the right person enough evidence to act.

If you want a website and SEO process tied to leads instead of mystery scores, get started with Your Web Team.