Introduction & Search Essentials

Before changing a tag or hiring a tool, write down which pages should attract which audiences. That list is the brief every later SEO change has to serve.

Block thirty minutes to confirm the site is reachable, titles are intentional, and Search Console (or the host's Google integration) is connected — then stop guessing.

When a site is new, compromised, or "just not on Google", open Search Essentials before any ranking checklist. Fix the gate first.

When a page underperforms, ask in order: was it crawled, is it indexed, is it eligible to be served for this query? Read How Search Works until those questions are automatic.

Once the site can appear in Search, work the Starter Guide top to bottom on the pages that matter. Treat it as the default "improve this site" playbook.

Verify the property early — before the first traffic scare. Use it for coverage, performance, and drops; do not wait until something is already on fire.

Name the situation first (new site, missing page, traffic drop, content polish), then open the matching lane. Do not start every problem in the Starter Guide.

Park appearance and structured-data work until the site clears Essentials, you can explain the three stages, and the Starter Guide checklist is honest. Then open those docs on purpose.

When a URL underperforms, classify the failure first — can Google show it, is it policy-safe, and does it follow the few high-leverage practices? Fix that class before tweaking anything else.

Reject any vendor pitch that implies you can buy organic placement. Budget that money into content, crawl health, and measurement instead.

Debug in order with Search Console: discovered? crawled? indexed? served? Treat each gate as its own problem rather than one vague "not ranking" ticket.

Spot-check key templates with URL Inspection. Confirm Googlebot can reach a 200 response with real content before you spend time on on-page polish.

Audit growth tactics against the spam policies before you scale them. If a channel only works by deceiving users or inventing signals, kill it.

Before publishing, answer what unique help this page gives a real person. If the honest answer is "rank for a keyword", rewrite or cancel the page.

Pull the actual phrases from Search Console and customer language into the title and H1. Match how people ask, not how your brand prefers to speak.

Audit primary navigation and in-content links as real `<a href>` elements. Confirm important URLs are reachable by clicking from a known page.

Ship the page, then put it in front of real communities, partners, and customers. Do not confuse this with buying links or running schemes.

When a template relies on JS, images, video, or rich results, open the matching Search Central guide for that surface and verify those requirements separately.

Pick the one or two result features your content type genuinely supports, implement those cleanly, and skip the rest.

For pages that must stay out of Search, allow crawling and use `noindex` (or the matching removal path). Document which templates are opted out and why.

Treat "can Googlebot fetch a working, indexable page?" as the first ticket on any new template — before ads, before outreach.

Debug eligibility in gate order: access → status → content. Stop at the first failing gate; do not jump to ranking theories.

When URL Inspection says the page is available to Google but not indexed, shift the investigation to content quality and duplicates — not another robots tweak.

Audit what loads without a session. Put true private surfaces behind auth, and block accidental public staging with the documented opt-out methods.

For every URL you want in results, confirm Googlebot is allowed to fetch it. Use URL Inspection on the live URL, not only on a staging copy.

When pages are missing, open Page Indexing and Crawl Stats the same day, then spot-check the worst URLs in URL Inspection.

Verify status codes for key templates with URL Inspection or `curl -I`. Fix soft-404s that return 200 and hard errors on URLs you want stored.

During incidents return 503 with Retry-After when you must, and watch Crawl Stats after. Never leave marketing URLs permanently on 404 if they should rank.

View the raw HTML Google receives and confirm the main substance is text in a supported format — not only painted in after client-side rendering.

If a template exists only to manipulate ranking, remove it. Do not try to "technically qualify" pages that fail the spam policies.

Never use robots.txt as a removal tool. If a URL must leave results, you need a method that still allows the crawl.

For removals: serve `noindex` (meta or header), keep the URL allowed in robots.txt, then verify with URL Inspection after recrawl.

When reviewing a growth idea, ask whether it helps a human decide or mainly exists to trick ranking or AI summaries. If the second answer is yes, kill it before it ships.

Watch Manual actions and Security issues in Search Console after any large content or link campaign. Fix the underlying practice, then request a review — do not reopen under a new subdomain.

Judge proposals by intent and user outcome, not by whether the tactic has a heading on the spam page.

Serve the same primary content to Googlebot that a signed-in or entitled user would see. Fix JS accessibility with progressive enhancement, not a crawler-only HTML fork.

Implement Flexible Sampling (or equivalent first-click-free patterns Google documents) so Googlebot receives the same article body a subscriber would, then verify with URL Inspection.

Publish one clear, browseable hierarchy with real local content. Delete or consolidate near-duplicate geo shells that add nothing beyond the query name.

If you acquire a domain, rebuild for the audience the name now serves with original value — or leave it parked. Do not wholesale-swap topics to harvest residual trust.

Patch CMS and plugins, rotate credentials, remove injected files, and use Search Console Security issues plus a malware scan after any unexplained traffic spike.

Delete any text or links that exist only for crawlers. If a phrase matters for ranking, put it in visible copy a human would actually read.

Keep progressive disclosure that helps users. Put the same substance in the HTML Google can render; do not stuff extra keyword paragraphs into visually hidden layers.

Write for one clear intent. Name the places or products you truly serve once, in context — never as a comma-separated dump at the footer.

Earn links with content worth citing. Treat any paid, gifted, or contractual link as advertising and qualify it — never buy "DA packages".

Audit every paid, gifted, or affiliate placement and add `rel="sponsored"` (or `nofollow`). Put the requirement in your media kit and CMS templates so new posts cannot ship bare.

Pull rankings from Search Console or a licensed provider API. Never point scrapers or headless farms at google.com/search.

Scan downloads against Google's unwanted-software rules, disclose install behaviour, and never intercept history to trap users on interstitial ads.

Ship the feature the title claims, or remove the page. If monetising with ads, the core tool still has to work without the bait.

Before generating at scale, define the unique value each URL adds. Exclude filler sections with `noindex` or delete them; do not hide scale behind multiple brand sites.

Cite and link out, or build original commentary, data, or tools on top of third-party material. Do not run a site whose only job is hosting copies.

Host third-party pages only when they serve your audience editorially. Kill or noindex coupon / lead-gen sections that exist solely to ride your domain authority.

Use redirects for moves, consolidations, and post-login flows. Never branch the destination by user-agent to show Search one URL and phones another.

Add original testing, pricing context, comparisons, or category navigation before attaching affiliate links. If you cannot add value, do not publish the page.

Moderate public surfaces, require verification for new accounts, nofollow UGC links by default, and set up alerts for sudden URL spikes in Search Console.

Fix the violating section in place. Do not clone it under a fresh path. Treat impersonation, fake support pages, and doxxing-adjacent content as emergency removals.