How to Structure a Page So ChatGPT Cites You Instead of Your Competitor

Structure each page to do three things: answer one buyer question in the intent the buyer actually has, say plainly who you are in schema an engine can read, and be indexed by Google. Then put something on the page that comes from doing the work, because that is the only part a competitor's page cannot also have. When someone shows me a page and asks why ChatGPT isn't citing it, those are the three things I check, in that order, before I read a word of the copy.

Here's what each one looks like, and what a page that did get named looked like.

Key takeaways

Check the schema first. A page with no Person, Organization or FAQ schema makes it hard for AI search, and for Google, to tell who you are. That is usually the first thing wrong.
Match the intent, not the topic. "Best ice cream flavors in Vancouver, Washington" is about ice cream in Vancouver and still answers the wrong question. The searcher wants shops.
If Google can't index the page, an engine probably isn't citing it. How retrievable a site is and how often it gets cited move together.
The page that gets named ties a specific to the problem. Anna's menopause page talked about fabrics and why, and her products were the natural next sentence. The pages it beat were lists of clothes.

The three things I check before anything else

Schema. If there is no Person schema, no Organization schema and no FAQ schema anywhere on the page, I stop there. That is going to make it really hard for not only AI search to tell who you are, but also Google, and all of its functionalities, to figure out who you are. An engine assembling an answer needs to know that this page belongs to a real business with a name, a person behind it and a place, and it reads that from structured data long before it reads your paragraphs.

Intent, meaning alignment. It is very easy to write a page about the right topic that answers the wrong question. Take "ice cream Vancouver, Washington." A page called "What are the best flavors of ice cream you can find in Vancouver, Washington?" is a similar question and it does not align. Someone typing that is probably looking for ice cream shops. Not the types, not the flavors, not the history. If the page is not answering what the buyer meant, it does not matter how well it is written.

Indexed. If the page is not indexed in Google, it is probably not being cited. When I did some research on this I found a very strong correlation between how retrievable a site is by Google and how often it got cited. Check that before you rewrite anything.

If the content isn't answering the question, it's not aligned with the intent, and there's no schema, you're not getting cited. Fix those three and the copy starts to matter.

What a page that got named looked like

Anna sells clothing, and she has a page about what to wear during menopause. Most of what exists on that question is a list: get this skirt, get this dress, here are twelve pieces. Anna went into the fabric instead. Which fabrics, and why each one is good for a woman going through menopause. And when she was talking about a specific fabric, the natural next sentence was the product she makes out of it, with a picture and a link, inside the post.

I'm pretty sure that is why she showed up best, and why the engines repeated her answer. She was tying the fabric to the problem rather than saying "if you're in menopause, get this dress." The engine had something worth using in the answer, and the product came along with it.

That is the structure to copy. Not "here are our products." The specific thing that solves the problem, explained, and your product as the place that specific thing lives.

The honest counterexample

The first page of mine an engine ever cited by name was about xanthan gum. I would love to tell you it was brilliantly structured. Honestly, I don't think there was anything special on it. Xanthan gum is a very popular ingredient in gluten-free baking, people use it to bind things when they substitute an ingredient out, and there was a lot of search volume for it. Most of the other content on that keyword was people selling xanthan gum, so mine was a different type of page for that question. All I know is that we get named a lot.

I include that because I don't want to make this sound like some magic trick. Sometimes you are the only page answering the question that isn't a shop. Structure still decides whether you can be quoted once an engine finds you, and it decides everything on the questions where you are not the only option.

How I lay out a page now

The same shape on every page, because it is the shape an engine can lift from:

The answer in the first two sentences. No warm-up. The engine pulls the opening and repeats it, so a page that clears its throat for three paragraphs loses to one that answers on line one.
Three or four key takeaways as bullets, each a standalone fact that makes sense on its own.
Headings phrased as the question a buyer would type. That is where the intent check lives. If you can't write the heading as something a buyer would actually say, the section is probably about the topic and not the question.
A short FAQ of three to five more questions, each answered in a few sentences, with FAQ schema on it.
Person and Organization schema naming who wrote it and which business it belongs to.

And then the part that is not a formatting rule. Put in something that only exists because you did the work. If your page just repeats the same stuff that's on nine other websites, there's not much reason for an engine to choose your page. But if your page contains information that comes from actually doing the work? That's different. Your real prices. The mistakes you see customers make. The way you handle a weird situation. The answer you give every single time somebody calls you. That stuff isn't sitting on 500 other websites.

One question per page, not one big guide

A single long guide covering everything about a topic feels thorough and reads, to an engine, as a page about a topic rather than an answer to a question. One page, one question, one job. If two questions have the same answer, merge them. If one question needs a different answer for a different buyer, split it. A set of those pages, linked to each other, is a citation cluster, and how to build your first one is the previous post.

Frequently asked questions

Does schema markup actually help ChatGPT cite my page?

It is the first thing I check, and the most common thing missing. Person, Organization and FAQ schema tell an engine who the page belongs to and what questions it answers, in a form it reads without guessing. A page without them can still be cited. It is just much harder for the engine to say your name with confidence.

Should I write one long guide or many short pages?

Many pages, one question each. A long guide is about a topic. An engine assembling an answer to a buyer's question wants the page that answers that question directly, and it favours businesses that show up across a topic, not once.

My page answers the question well but it still isn't cited. What now?

Check the three things in order: schema on the page, whether the heading really matches what the buyer meant, and whether Google has indexed it. Then ask whether the page says anything that isn't on nine other sites. If it doesn't, that is the fix, and how to know if your cluster is working covers how to check whether it worked.

How long until ChatGPT starts citing a page built this way?

I don't know, and I would not trust anyone who gives you a number. What I can tell you is what to check every week so you know the day it happens.

If you have a page you can't figure out, shoot me a message on LinkedIn with the link. I'll tell you which of the three it is.