New page tech check

Runs a new page through the full technical checklist: meta and content, indexability, speed — one request instead of three.

Launching a new page usually means checking several independent things at once: are the meta tags and headings right, is the page accidentally blocked from indexing, does it load fast enough. Each check is simple alone, but together they turn into a routine that's easy to rush right before a release — exactly when critical details get missed.

What it does

Given a page URL, the skill checks three blocks at once: content (title, description, H1, heading structure, text quality, internal links, key image alt text), indexability (robots.txt and noindex rules, canonical target, sitemap inclusion), and speed (whether the page clears Core Web Vitals thresholds).

What you get

A structured checklist across all three blocks, split into two priority lists: "fix before launch" for real blockers, and "improve later" for non-critical findings that don't need to hold up the release. It closes with a single verdict — ready to publish or not. Use it as the last step before launching any new page, especially in a pipeline of similar pages where one shared template bug could otherwise repeat across dozens of future pages.

FAQ

How is this different from the meta tag check?
The meta tag check only looks at title, description and H1. This one is broader — content, indexability and speed together, in a single request.
What counts as a launch blocker?
Things like a page accidentally blocked from indexing, missing from the sitemap, or failing speed thresholds — those land in the "fix before launch" list.
What can wait until after publishing?
Minor findings, like a non-optimal alt text on a secondary image, go into a separate "improve later" list instead of blocking the launch.

More skills in this category

Learn more in the SEO guide

Didn't find the right skill?

Describe your task in your own words — the assistant will build a skill for you in a couple of minutes.

Create your own