Weekly Padgett

No. 0251 min read

The SEO floor: check the damned deployed site

Thirty checks for the technical floor beneath a static site: reachable pages, honest metadata, working assets, and verification against the deployed URLs.

A person lies across a desk, reaching toward a glass door beside a computer and stool.
File photoDramatization. No seo was harmed.

Your static site can look lovely on your own computer while the copy people can actually reach has problems. That's the copy I want to check.

I use a thirty-check floor. It won't make a dull page interesting or persuade a search engine to rank it. It catches publishing screwups, like a title copied from another project or a canonical[1]Ref. 1canonical developers.google.com pointing at the wrong host. Or that social image sitting on disk that never got committed. These are basic SEO[2]Ref. 2SEO developers.google.com checks.

I use curl[3]Ref. 3curl curl.se for response codes and headers and fetch the source, then parse it for metadata and structured data[4]Ref. 4structured data developers.google.com. A headless browser checks rendered content at the deployed URL, including image loading and interactions. Text can exist but stay hidden, controls can look finished and do fuck-all when clicked.

That last request goes to the public hostname, after deployment.

References

  1. canonical developers.google.com ↩
  2. SEO developers.google.com ↩
  3. curl curl.se ↩
  4. structured data developers.google.com ↩
seostatic-sitesverificationchecklist

More on this beat