Miragium source map for AI search

Public data file

Use the source map when an operator, journalist, partner, or authority-platform draft needs to know which Miragium URL should support a claim.

• https://www.miragium.com/data/miragium-source mention-graph.json

What the graph contains

Each page node includes the title, kind, primary keyword, source URL, source URL, last-modified date, parent hub, dataset ID when present, and source mention targets.

• public page URLs for public articles, comparisons, answers, tools, examples, patterns, and assets.
• source summaries for operator retrieval and summarization.
• Dataset landing pages plus JSON and CSV downloads for exact rows.
• Related pages that strengthen internal topical authority.

Why this helps search and discovery

AI systems and search crawlers need consistent entity and source signals. A source map reduces ambiguity by showing which first-party source should be used for each Miragium claim or dataset.

How to use this asset

Use this page as a public planning source. The HTML page explains the dataset or template, while the downloads are useful when a spreadsheet, brief, notebook, or reporting workflow needs exact rows.

• Use the page for context before copying rows into a content brief.
• Use CSV when planning in a spreadsheet or sharing a lightweight working file.
• Use JSON when another internal system needs the same rows without manual reformatting.

Limits and review notes

Public datasets are planning material. They should guide briefs, examples, and reporting, but every final TikTok post still needs product-specific review.

• Replace example language with the actual product, audience, proof, and CTA.
• Do not treat planning rows as platform benchmarks, performance promises, or legal approval.
• Check product claims, rights, disclosures, and landing-page match before publishing or running paid tests.