Get an article
GET /content/by-slug/{slug}: one published article with its related links.
GET https://api.seoforsaas.dev/api/v1/projects/{projectId}/content/by-slug/{slug}GET https://api.seoforsaas.dev/api/v1/projects/{projectId}/content/{articleId}Use the slug on an article page. Use the ID if your site stores IDs. Both return the same object, and neither changes when an article is rewritten.
curl "https://api.seoforsaas.dev/api/v1/projects/YOUR_PROJECT_ID/content/by-slug/how-google-decides-what-to-show" \ -H "Authorization: Bearer $SEOFORSAAS_CONTENT_KEY"Response
{ "success": true, "data": { "id": "…", "slug": "how-google-decides-what-to-show", "title": "…", "blocks": [], "seo": {}, "related": [{ "title": "How to write a sitemap", "href": "/blog/how-to-write-a-sitemap" }] }}A draft, an archived article, and an unknown slug all return the same 404. related is computed when you read, from the articles published by then, so older articles gain links to newer ones on your next build; each href already starts with your base path (Articles live under).