Skip to content
Docs

SEO for your article pages

The feed gives you everything a well-formed article page needs. This is where each field goes.

On the page From the article
<title> title
<meta name="description"> description
<link rel="canonical"> url
<h1> title, once
Cover image, with its alt text cover.src, cover.alt
Byline author.name, linked to author.url when it has one
Published and updated dates publishedAt, modifiedAt
JSON-LD structuredData, when it isn’t null
Open Graph tags title, description, url, cover.src

Every article has the address CitedSEO expects it to live at: your site, then your blog path, then its slug. The canonical address and the structured data both use it.

So route by slug under the same path. If the feed says https://example.com/blog/how-to-brew-green-tea, serve the article at /blog/how-to-brew-green-tea.

If your articles live somewhere else, say /guides, change the site’s blog path in the app’s settings so new articles get addresses under it. Don’t rewrite url on your side: the structured data would still point at the old address.

Draw articles on the server or at build time, not in the browser alone. A page that only fills in after JavaScript runs may be read as empty by search engines and by the AI assistants that cite pages. Every framework guide renders on the server.

The body is written to be quoted: an answer at the top, clear sections, an FAQ and a list of sources. Show all of it.

  • Keep the answer or key takeaways at the top, where they are.
  • Keep the sources list. It is what the article’s facts rest on.
  • Don’t drop the FAQ if you keep the structured data: the FAQPage data describes questions that must be visible on the page.

The body starts at the first line of the article and uses h2 and below, so your page’s h1 is the title and there is exactly one.