Brand your named frameworks for AI attribution

Why this matters

Prefix your framework with your brand name and repeat the exact phrase everywhere you publish.

Before you start

• At least one original framework or named method already published on the site
• Editorial control over the pages and channels where it appears

How to apply it

1. Pick the framework to rename General best practice

   Choose one original method you already publish under a generic label and note every URL, heading and asset where that label appears.

   Check: A list of URLs exists that each contain the generic label in the title, H1 or body copy.

2. Coin the branded name

   Prefix the concept with your brand, keeping it short and typeable, for example "The Acme Content Scoring Matrix". Use one spelling and capitalisation.

   Check: The chosen string returns zero exact-match results when searched in quotes before you publish it.

3. Replace the generic label on existing pages General best practice

   Update titles, H1s, body copy and image alt text on every page from the list so only the branded name is used going forward.

   Check: A site search for the old generic label returns no remaining pages, and the new name appears in the page source of each updated URL.

4. Repeat the exact phrase on every channel you publish on

   Use the identical branded string in blog posts, docs, video titles, newsletters and social posts rather than paraphrasing it.

   Check: A site: query plus the branded phrase in quotes lists your pages, and the same phrase appears verbatim on your external profiles.

5. Check the attribution after a few weeks General best practice

   Search the branded phrase in Google and ask an AI assistant about the topic to see whether your site is named alongside the concept.

   Check: The exact-phrase search returns your site on page one and the assistant answer names your brand with the framework.

<goal>
index anchor locale heading measure query sitemap layout crawl canonical section markup effort report.
</goal>

<context>
render pipeline measure redirect schema content content caching effort render effort measure canonical crawl.
</context>

<discover_first>
content serp serp signal route query render caching heading payload route heading effort layout.
</discover_first>

<constraints>
image index alt index section route verify sitemap crawl audit link layout template canonical.
</constraints>

<plan>
payload template metadata report layout content heading metadata intent locale effort breadcrumb effort crawl.
</plan>

<verify>
crawl locale anchor template link locale route priority crawl heading cluster cluster signal heading.
</verify>

<report>
redirect content verify priority markup locale metadata serp crawler sitemap section template render route.
</report>

Source: @nicholasdulait on 2026-10-16 · original post · report an error