What's new at OptimAIze
Every feature, crawler, and schema generator we ship — in one timeline.
- 2026-06-12v2.4.0BlogSEO
Blog engine v2 + related posts
Articles now auto-tag during generation, sitemap freshness signals for new posts, and a related-posts module at the bottom of every article.
- 2026-06-08v2.3.0Programmatic SEOContent
Programmatic SEO expansion
Shipped /ai-engines, /locations, and /glossary route families. Net +120 indexable pages with JSON-LD, FAQ schema, and internal linking.
- 2026-05-28v2.2.0MonitoringGEO
AI Citation Tracker beta
Live monitoring of brand mentions in ChatGPT, Perplexity, Claude, and Google AI Overviews. Weekly email reports with trend lines.
- 2026-05-15v2.1.0ToolsAgents
ai-plugin.json generator
New tool that writes an AI-plugin manifest for any domain. Helps agent frameworks discover your site as an actionable endpoint.
- 2026-05-01v2.0.0GEOScoring
Generative Engine Optimization (GEO) scoring
Replaced the legacy SEO score with a dedicated GEO score that measures AI-readiness: llms.txt, AI crawler permissions, entity clarity, and schema coverage.
- 2026-04-10v1.9.0i18nSEO
Multilingual launch — 12 languages
Full hreflang support for English, Spanish, French, German, Portuguese, Italian, Chinese, Russian, Arabic, Japanese, Persian, and Hindi.
- 2026-03-22v1.8.0IndexingPerformance
IndexNow + Bing auto-ping
Every new programmatic page and blog post is automatically submitted to Bing via IndexNow, cutting indexation time from weeks to hours.
- 2026-03-01v1.7.0SchemaAEO
FAQ schema + Speakable markup
Added FAQPage and Speakable JSON-LD to all guides and tools. Improves voice-assistant and AI Overview surfacing.
- 2026-02-10v1.6.0ExportAgency
PDF audit reports
One-click export of a branded PDF with scores, issues, generated files, and a task checklist. Built for agencies sharing audits with clients.
- 2026-01-15v1.5.0ToolsGEO
llms.txt generator v1
The first public version of our llms.txt generator. Crawls your site, infers structure, and outputs a deploy-ready machine-readable manifest.
- 2025-11-20v1.4.0CrawlersGEO
PerplexityBot + ClaudeBot coverage
Expanded AI crawler detection and robots.txt rules to cover PerplexityBot, ClaudeBot, and anthropic-ai user agents.
- 2025-09-05v1.3.0AEOScoring
Answer Engine Optimization (AEO) score
Added a second score focused on answer-first content, FAQ schema, and Speakable markup. Complements the GEO score for full AI-search coverage.
- 2025-06-18v1.2.0ToolsSchema
JSON-LD + robots.txt generators
Shipped standalone tools for JSON-LD schema and AI-aware robots.txt. Every output is validated against Google's rich-results test.
- 2025-04-01v1.1.0LaunchScanner
Free scanner public beta
Opened the free GEO scanner to the public. First 1,000 audits revealed that 71% of sites had no machine-readable summary at all.
- 2025-01-10v1.0.0Launch
OptimAIze launch
Initial release of the GEO and AEO scanner. Six files generated per scan: llms.txt, robots.txt, sitemap.xml, JSON-LD, ai-plugin.json, and FAQ schema.
Want the next update first?
Follow the blog or run a free scan to see what the current version of OptimAIze recommends for your site.
Read release notes as changes, not outcome promises
A release note describes what changed in the product. It does not prove a lift in traffic, guarantee citation placement or establish adoption by an AI vendor. Check whether a change applies to the tool or workflow you use, then compare the current result with your retained baseline.
Verify a change on your own published site
After updating generated files or recommended markup, inspect the live domain and representative URLs. Cache behavior, CMS settings and deployment permissions can differ from a preview. Keep your previous configuration and note the date so regressions can be reversed and changes can be compared fairly.
Keep a record of what changed
Save the original URL, input, date and evidence before editing. Verify the deployed page or file, document the changes and repeat the same checks. Separate technical validity, correct answer representation and qualified visits; none should be used as a substitute for the others.
Evidence and next actions
| Check | Evidence to retain | Action |
|---|---|---|
| Access | Public status and useful response body | Fix barriers before rewriting |
| Accuracy | Visible facts and supporting primary sources | Correct unsupported statements |
| Markup | Valid syntax that matches the page | Remove invented reviews and properties |
| Outcome | Comparable responses and referral activity | Report observations without guarantees |
Implementation checklist
- Use the tool or guide matching the problem.
- Verify important facts against current primary documentation.
- Keep private data out of published files and support requests.
- Check changes on the real domain.
- Retain comparable before-and-after evidence.
A repeatable workflow
- 1Establish a baseline
Save the page URL, date, language, target market and exact questions before editing. Record what the page actually says and what each tested answer cites; a mention without a source link is not a citation.
- 2Make one coherent change
Resolve the clearest failure first, then check the published page rather than only an editor preview. Keep an implementation log so unrelated redesigns, campaigns or product changes are not mistaken for the effect of this work.
- 3Repeat and compare
Repeat the same questions and technical checks after deployment. Keep engines and measurement conditions consistent, report sample size, and inspect answer accuracy alongside citations. A single response is not a stable ranking.
More questions answered
- Does this guarantee an AI citation?
- No. A crawlable, accurate page can still be omitted. Retrieval, source selection and generated answers vary between products and requests; these checks improve the evidence available, not guarantee placement.
- How do I tell whether an improvement worked?
- Compare like-for-like checks and retain the underlying evidence. Track correct brand mentions, source-linked citations and qualified referral visits separately. Do not call a technical score a traffic forecast or attribute every change to one edit.