A pre-publish review covering intent, title, URL, headings, links, images, metadata, canonical tags, mobile experience, and distribution readiness.
1–4: Intent and usefulness
Confirm the article answers a clear question, matches the audience's level of knowledge, provides original or genuinely useful information, and has a clear next step. If the page is only a rewritten summary of results that already exist, improve the value before polishing metadata.
5–8: Title, heading, and URL
Check that the SEO title and H1 describe the same subject, the title is specific rather than sensational, the slug is short and readable, and the canonical URL uses the preferred HTTPS address. Avoid changing a live slug without a redirect plan.
9–12: Structure and readability
Use headings to organize real sections, keep paragraphs readable on a phone, explain technical terms when the audience needs it, and use lists or tables only when they improve comprehension. A well-structured article is easier to scan and easier to maintain.
13–16: Links
Verify important internal links, add links from relevant older pages to the new article, check external sources, and remove broken or redirected URLs where a direct final URL is available. Anchor text should describe the destination naturally.
17–20: Images and metadata
Resize and optimize images, check alt text where appropriate, verify the featured/social image, and review the meta description. Make sure Open Graph output uses a reachable image URL and that social crops do not cut off essential text.
21–23: Technical checks
Open the page while logged out, test it on mobile, and confirm that indexing controls, canonical tags, robots rules, and status codes are correct. A visually perfect article cannot perform well if the public page is accidentally blocked or redirects incorrectly.
24–25: Distribution and measurement
Prepare campaign URLs only for channels you will analyze, then test the exact link that will be shared. Record the final URL, short aliases, and campaign naming in the editorial task so future updates do not require reverse-engineering the launch.