TL;DR
Every brand on Context Memo gets a dedicated branded subdomain (e.g. yourcompany.contextmemo.com) the moment they're onboarded. It's live, fully branded, and the AI crawlers can see it immediately. When you become a paying customer, we white-label it onto your own domain with a single CNAME record. But the subdomain is just the surface. The real work is what happens after each memo publishes: IndexNow submissions to Bing, Yandex, and Seznam; auto-generated sitemaps and llms.txt files; bot crawl detection per memo; AI-referred traffic attribution per memo; automatic internal backlinking; engagement-tiered visibility scanning; and 301 redirect management. None of this requires you to lift a finger.
How a brand goes live
When you're onboarded: subdomain created automatically
The moment a brand is added to Context Memo, we provision a dedicated subdomain off our root: yourcompany.contextmemo.com. It's a fully separate site from contextmemo.com — separate SEO, separate crawl, separate content. We host it, secure it with HTTPS, and configure the DNS. You don't do anything.
Within hours, your subdomain is:
- Branded to your company (logo, colors, typography pulled from your corporate site)
- Crawlable by Google, Bing, and every named AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.)
- Listed in your sitemap.xml and llms.txt
- Ready to publish memos against
When you become a paying customer: optional white-label to your own domain
When you're ready to host the channel on your own domain — typically as a subdomain like ai.yourcompany.com or learn.yourcompany.com — your IT team adds one CNAME record at your DNS provider (GoDaddy, Cloudflare, Route 53, Namecheap, whatever you use). The CNAME points to our system. It takes about 5 minutes of IT work.
We handle the rest: SSL certificate provisioning, HTTPS enforcement, 301 redirects from the old subdomain so existing AI citations keep resolving, and updates to your sitemap and structured data so search engines and AI models see the new canonical URL.
The content stays exactly the same. Only the URL changes. This is the same mechanism HubSpot, Webflow, Vercel, and every other hosted-content platform uses to let you serve their pages on your domain.
What we do after each memo publishes
This is the work most marketing teams don't realize they need to do — and that nobody on a typical content team has the engineering capacity to do consistently.
1. IndexNow submission
The moment a memo publishes, we submit its URL to the IndexNow protocol — a real-time push-notification system for search engines. We submit to three endpoints simultaneously: api.indexnow.org, bing.com/indexnow, and yandex.com/indexnow.
This matters because Bing's index is what powers ChatGPT search. The faster Bing picks up your content, the faster it becomes citable in ChatGPT's real-time answers. IndexNow can get content indexed in minutes rather than days or weeks.
2. Auto-generated sitemap.xml and robots.txt
Every published memo is automatically added to your subdomain's sitemap.xml. Your robots.txt is configured to explicitly allow all major AI crawlers, including:
- GPTBot (OpenAI / ChatGPT)
- ClaudeBot (Anthropic)
- PerplexityBot (Perplexity)
- Google-Extended (Gemini)
- Bingbot (Bing + ChatGPT search)
We don't block them. Most corporate sites accidentally block one or more of these because the default rules from their CDN or security tool are restrictive. We've seen brands lose AI visibility for months without realizing their own robots.txt was the problem.
3. llms.txt and llms-full.txt generation
We generate and maintain llms.txt (a curated index of the most important pages) and llms-full.txt (the full content) — the emerging standard for telling AI models which content is canonical reference material. These files are updated automatically every time you publish or update a memo.
Think of llms.txt as a hand-curated map that says to AI models: "Don't scrape 200 pages to answer a question about this brand. Start here." It's designed to be cheap for AI providers to consume, which makes them more likely to cite it.
4. Schema.org structured data
Every memo is automatically wrapped in JSON-LD structured data (Article, FAQPage, Organization, Product schemas where applicable). This helps:
- Google show your content in rich results, AI Overviews, and Knowledge Panels
- AI models parse the content reliably without ambiguity
- Citation tools attribute the content back to your brand correctly
This is engineering work most marketing teams put on the roadmap and never actually ship.
5. Automatic internal backlinking
When a new memo publishes, we analyze your existing memos and inject contextual internal links between them. Both directions: the new memo links to relevant older memos, and older memos get updated to link to the new one where appropriate.
Internal linking is one of the highest-leverage SEO activities you can do, and it's the one most consistently neglected because it's tedious manual work at scale. We automate it.
6. 301 redirect management
If a memo's slug changes (because we've refined the title or the URL structure), we automatically create a 301 redirect from the old slug to the new one. This preserves any inbound links, AI citations, and SEO equity. Most CMS platforms require manual redirect entries; we handle it as part of the pipeline.
7. Bot crawl detection (per memo)
Our middleware inspects every incoming request and identifies named AI crawlers by user agent and verified IP ranges. We log every visit from GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others to a bot_crawl_events table — attached to the specific memo that was crawled.
This tells you which AI models are actually consuming each piece of your content — not just whether you're being crawled, but which memos, how often, and at what cadence. Most brands have no visibility into this at all.
8. AI traffic attribution (per memo)
When a real human visitor arrives at your memo from an AI assistant — referrer is chat.openai.com, claude.ai, perplexity.ai, you.com, phind.com, etc. — we log it against the specific memo they landed on. You see exactly which AI sent the visitor, which memo they read, and how engaged they were.
This is the metric that matters most: AI as a real acquisition channel, measured at the memo level. Until you can measure it, you can't optimize against it.
9. Per-memo performance dashboard
Every memo has its own performance view that combines the signals above: bot crawl frequency over time, AI-referred human visits, total page reads, and which AI platforms are driving the most attention. This is the data that tells you which memos are pulling weight and which need iteration — not as an aggregate brand score, but at the level of the individual asset.
10. Engagement-tiered visibility scanning
Separately from the passive data above, we actively scan AI models against your target buyer prompts to see how your brand appears in their answers. We don't run every model every day on every prompt — that would be wasteful and expensive. Instead, scanning frequency scales with engagement:
- Low-priority prompts get checked roughly monthly, against one model
- Higher-engagement prompts get checked weekly, across multiple models
- Top-priority and hot prompts get the most frequent multi-model coverage
This is deliberate budget allocation: more inference spend goes to the prompts that actually move pipeline, less to long-tail prompts we already know the answer for. The result is visibility tracking that's both cost-efficient and focused on what matters to your funnel.
11. HubSpot mirroring (optional)
If you've connected your HubSpot account, every published memo is also mirrored as a HubSpot blog post — same content, same formatting, with IndexNow submission against your HubSpot URL too. This lets you keep your existing HubSpot reporting and CRM workflows intact while benefiting from the Context Memo subdomain.
Why this matters
Most of the work above is the kind of engineering hygiene that AI visibility actually depends on, but that no content team has the time, tools, or technical resources to do consistently.
The typical alternative looks like this: a marketer writes a blog post, hits publish in their CMS, and assumes search engines and AI models will eventually find it. They don't check whether the page is indexed in Bing. They don't check whether GPTBot has crawled it. They don't know whether llms.txt exists, let alone whether their site has one. They don't know if their robots.txt is blocking the AI crawlers they need to reach. They don't know which AI assistants are sending humans to which page, or which crawlers are reading which memo.
Context Memo does all of this automatically, for every memo, every time. The subdomain is just the address. The machinery behind it is the product.
Frequently asked questions
Do I need to give Context Memo access to my DNS? No. We host your subdomain entirely on our infrastructure. When you're ready to white-label onto your own domain, your IT team adds one CNAME — they never give us their DNS credentials.
Can I see what AI crawlers are hitting each memo? Yes. Crawler activity is logged per memo and surfaced in your dashboard, broken down by crawler, memo, and time.
What happens to my SEO if I move from your subdomain to my own domain? We set up 301 redirects from every old URL to the new canonical, update your sitemap and llms.txt, and resubmit to IndexNow. Existing AI citations continue to resolve.
Will Google penalize my main site for the memo content? No. The subdomain is a separate site as far as Google is concerned. Your main domain's SEO is fully isolated.
Does Context Memo work alongside HubSpot, WordPress, Webflow, etc.? Yes. We don't replace your CMS. We operate as an additional content channel optimized specifically for AI visibility, sitting next to whatever you're already running.
Who is responsible for the content? You are. We generate drafts grounded in your existing brand voice and approved facts, but every memo is owned by you, edited by you, and published on your timeline.
If you ever want to break up with us
Honest disclosure: as of May 2026, no Context Memo customer has ever not renewed. That is less a flex (we are new) and more an explanation for why this section is hypothetical rather than battle-tested. We are writing it anyway, because how a vendor handles your exit says considerably more about them than how they handle your onboarding.
Here is the truth about how leaving would work today:
What is already in place:
- Self-serve data export from your dashboard. Memos, prompts, scan history, and competitor records are available as CSV or JSON. The brand context behind your AI Brand Memo is a structured JSON object we can hand you on request.
- You keep your custom domain instantly. If you white-labeled onto
ai.yourcompany.com, you remove the CNAME record at your DNS provider and the subdomain is yours to repoint elsewhere within minutes. There is nothing to release back to us. - Per-URL 301 redirects on request. Our redirect infrastructure is in routine production use today (the memo system uses it for slug renames). For an offboarding scenario, we configure redirects from your old Context Memo subdomain URLs to wherever you want the content to live next, so existing AI citations and inbound links continue to resolve.
- Hard delete on request. A GDPR-compliant endpoint purges all of your data irreversibly if that is what you want.
What we would build the first time someone actually needs it:
- A single-download archive of everything (every memo as
.md, brand context as JSON, all data as CSV) instead of the current per-type exports. About 30 minutes of work. - A subdomain-wide archive mode that redirects every URL on
yourcompany.contextmemo.com/*to a target pattern, instead of configuring redirects per URL. About half a day.
We are being this explicit because we would rather earn your renewal on the work we do than on the friction of leaving. We stop charging you the moment you say go.