Content Genius was inserting incorrect year references — such as "in 2023" or "as of 2023" — into AI-generated article headings and body content. The fix has been deployed; articles generated now include correct date context.
Note: This article covers only the incorrect year reference issue. Several related but separate known issues are tracked independently:
- Incorrect Brand Vault assignments across projects (CG-141, resolved) — Regenerate affected articles to pick up the fix.
- Brand Vault sync mapping errors causing missing logos, images, or incorrect social profile assignments (CG-1761, resolved) — Regenerate affected articles to pick up the fix.
- Articles missing target keywords, Topical Terms, or competitor analysis (CG-1792, under investigation) — Contact support and reference your account for investigation.
- Excluded Brand Vault terms still appearing in generated content (CG-1576, resolved) — Regenerate affected articles to pick up the fix.
- Brand Vault social media links not saving to the database across accounts (SPE-732, active) — Do not re-enter the data repeatedly; contact support and reference SPE-732.
- Brand Vault logos or images visible in the backend but not rendering on the frontend — This is a separate rendering issue from CG-1761; contact support so the team can investigate.
- Unable to create a new Brand Vault due to a false "domain already exists" error (CG-1886, awaiting release) — Contact support in the meantime so they can flag your account.
🔍 What's Happening
Date context was missing from the prompts used during heading outline and content generation. Without this signal, the AI model defaulted to stale year references, making generated content appear factually outdated even when the article topic had no connection to that year.
- Symptom: Generated articles contain phrases like "in 2023" or "as of 2023" regardless of your chosen topic.
- Who is affected: Articles generated before the fix was deployed. Contact support via the in-app chat or by submitting a ticket at support.searchatlas.com with your account ID and generation timestamps so the team can confirm whether your articles fall within the affected window. The team typically responds within one business day.
- Where it appears: Both article headings and body paragraphs — including introductions, section headings, and inline references throughout the generated content.
Articles generated after the fix was deployed will no longer include stale year references.
🛠️ Workaround Steps
If you have existing articles that contain incorrect year references, choose either option below.
Option 1 — Edit the article manually
- Open the affected article in the Content Genius editor.
- Search for incorrect year references (e.g., "2023").
- Replace each instance with the correct year.
- Save your changes.
Option 2 — Delete and regenerate
- Delete the affected article.
- Regenerate it — the fix is live, so the new version will include correct date context automatically.
Tip: To reduce year ambiguity in future articles, include the target year explicitly in your topic or brief — for example, add "2026 guide" to your topic input to anchor the AI to the correct time context. If you generated a high volume of articles during the affected window, use your workspace's article search to locate generations containing "2023" or "2024" so you can review them in batches rather than one by one.
📡 Engineering Status
This issue has been identified and resolved. The fix is deployed to production — date context is now correctly passed into both the heading outline and content generation prompts. By "correct date context," we mean the AI now references the current calendar year by default (e.g., 2026) unless you specify a different year in your topic or brief. Articles you generate going forward will no longer contain incorrect year references.
📞 When to Contact Support
Reach out to the support team if any of the following apply:
- You regenerate an article and still see incorrect year references.
- You cannot access the Content Genius editor to make manual corrections.
- You need help identifying all affected articles in your account, or confirming whether a generation falls inside the affected window.
- Your Brand Vault social media links are not saving across accounts (SPE-732, active) — reference SPE-732 when you reach out, and avoid re-entering the data repeatedly while the fix is in progress.
- Your Brand Vault logos or images are visible in the backend but not rendering on the frontend — this is a separate rendering issue from CG-1761 and requires support investigation.
- You are unable to create a new Brand Vault due to a false "domain already exists" error (CG-1886, awaiting release) — contact support so they can flag your account until the fix ships.
- You suspect a different issue — such as incorrect Brand Vault assignment across projects (CG-141, resolved — regenerate affected articles to confirm the fix), Brand Vault sync mapping errors causing missing logos, images, or incorrect social profile assignments (CG-1761, resolved — regenerate affected articles to confirm the fix), or articles missing target keywords, Topical Terms, or competitor analysis (CG-1792, under investigation).
When you contact support, include the article title and the specific incorrect year references you are seeing. Reach the team through the in-app chat or by submitting a ticket at support.searchatlas.com — expect a response within one business day.
🌀 This issue is resolved — articles you generate now reflect the correct date context. A quick edit or regeneration will bring any existing affected articles fully up to date, and the team is here if you need further assistance.