TECHNIQUE 01
One URL per page, one page per URL
Duplicate URLs (http vs https, www vs non-www, trailing-slash variants, query strings) split your ranking signals across copies of the same page. Pick one canonical form and force it at the server level with 301s, not with JavaScript.
Run curl -I against the http://, www, and no-slash variants of your homepage. Each should answer with a single 301 straight to the canonical URL — no chains.
TECHNIQUE 02
Ship a real sitemap and keep it honest
A sitemap is a promise to crawlers: these URLs exist, they answer 200, and they are worth indexing. Sitemaps with 404s, redirects, or noindexed pages teach Google to ignore yours.
Regenerate sitemap.xml on every deploy and spot-check 10 random URLs from it monthly — every one should return 200 and a canonical tag pointing to itself.
TECHNIQUE 03
Return real HTTP status codes
A missing page must answer 404, not 200 with an error layout (a soft 404). Soft 404s poison the index with junk URLs and burn crawl budget that should go to real pages.
In Google Search Console, open Pages → Not indexed and look for the Soft 404 bucket. Anything listed there needs a true 404/410 or a 301 to a real equivalent.
TECHNIQUE 04
Make speed a budget, not a wish
Core Web Vitals are a tiebreaker, not the whole game — but slow pages lose users before ranking even matters. The biggest wins are boring: compress images, preload the hero asset, cache static files at the edge.
Set cache headers by file class: HTML no-cache, hashed JS/CSS immutable for a year, images for 30 days. Then test LCP on a mid-range phone over 4G, not on your laptop.
TECHNIQUE 05
Render-test your JavaScript
If your content only appears after client-side JavaScript runs, you are betting your visibility on a second, delayed indexing pass — and AI crawlers mostly do not execute JavaScript at all. Server-render or statically export anything you want discovered.
Run curl against your key pages and grep for your main headline. If it is not in the raw HTML, neither Google's first pass nor any AI engine can see it.
TECHNIQUE 06
Kill redirect chains
Every hop in a redirect chain leaks crawl budget and slows users. Chains usually accumulate silently: http → https → www → final URL is three hops for one page view.
Crawl your site with a tool like Screaming Frog (or a script) and flag any URL that takes more than one hop to resolve. Collapse them to single 301s at the origin.