You coined a framework. You named a method. You built a system and documented it.
Then somebody else wrote about it. Google picked up their version as the canonical source. Six months later, Perplexity credits them — not you — when it synthesizes an answer that uses your idea.
This isn't theoretical. I've watched it happen to authors, consultants, and indie creators three times in the last year. The fix isn't more blog posts. The fix is a set of deliberate origination signals that tell Google's entity graph — and, downstream, every AI retrieval pipeline — that you were the source.
Today I'm releasing a tool that produces all of them.
What it does
Framework Origination Signal Generator takes a short description of the method or framework you created and outputs five deliverables:
- DefinedTerm + CreativeWork + HowTo JSON-LD you paste into the
<head>of the canonical article on your site - A Wikipedia stub article template formatted in Wikipedia markup (with the honest caveat that Wikipedia has a strict notability bar)
- An Internet Archive submission checklist covering Wayback Machine, Archive.org items, Zenodo DOI, ORCID linking, and Archive Scholar
- A press-release template you can drop into EIN Presswire, Accesswire, or a local Business Journal
- A canonical on-site article outline structured to rank as the "defined by" source
It also scores the origination signal strength of your inputs out of 100 — so you know which fields are strong and which need more work before you file anything.
Why schema alone isn't enough
Schema.org's DefinedTerm type exists specifically for this purpose. It lets you mark up a named concept with a creator, a first-publication URL, and a definition. Google reads it. AI systems read it.
But schema on one page isn't a claim the entity graph will believe. Think of it as your signature. What makes the signature load-bearing is:
- Multiple independent URLs that repeat the claim — your canonical article, a Wikipedia stub (if notability holds), Internet Archive snapshots, a Zenodo DOI record, a press release on a wire service, a Medium republish with rel=canonical pointing home
- Timestamped proof that you published first — a Wayback Machine snapshot of your original article, a Zenodo DOI dated before any competitor's page, an ORCID work record linking to it
- A persistent identifier — ORCID, Zenodo DOI, or OpenLibrary OLID — that AI systems treat as authoritative
The tool builds the scaffold for all of that in one pass. You fill in five fields. It produces the JSON-LD, the Wikipedia markup, the checklist, the outline, and the press release — all stamped with your name, your year, and your URL.
When not to use it
Two caveats that are in the tool itself but worth repeating here:
Don't file a Wikipedia stub unless you have at least two independent secondary sources. Major press. Peer-reviewed publications. Established industry news outlets. Without them, Wikipedia editors will delete the article within days and you'll have burned your credibility with the reviewer pool.
Don't chase origination if the concept isn't genuinely novel. Schema can claim anything; the entity graph accepts only what's novel enough to merit a distinct identifier. If your "framework" is a rebrand of something that has existed since 2015, the graph will fold you back into the parent entity regardless of markup.
The tool's input form is designed to surface both failure modes. If your origination-signal score comes back below 60, that's a signal to do more work on the method itself — not to file anyway.
Workflow suggestion
Here's how I'd use the tool for a real framework launch:
- Write the canonical article first. Use the "On-site canonical article outline" the tool generates as the template. Name the framework, define it, walk through the steps, include two or three case studies.
- Publish on your own domain. Fresh URL, clean canonical tag.
- Paste the DefinedTerm + CreativeWork JSON-LD into the
<head>. Validate with search.google.com/test/rich-results. - Snapshot with Wayback Machine.
web.archive.org/save/your canonical URL. This timestamps "first described on this date." - Mint a Zenodo DOI. Upload the article as a PDF with you as sole author. The DOI becomes your persistent identifier.
- Link the DOI to ORCID. If you don't have an ORCID, register one — it's free, takes five minutes, and AI systems weight ORCID-linked works heavily.
- Distribute the press release. EIN Presswire runs about $99 for a broad release. You get a handful of independent URLs naming you as the coiner within 48 hours.
- Wait. Entity graphs take four to twelve weeks to reconcile. Re-audit the canonical page with AI Citation Readiness Audit after 30 days and tune from there.
Open the tool
Open the Framework Origination Signal Generator →
It ships alongside three siblings: AI Citation Readiness Audit, Entity Citation Radar, and Newsletter Swap Matchmaker. All live in the tools hub.