SEO and GEO for small businesses: one public truth

Key takeaways

• Search and answer engines should repeat the same facts. GEO is extractability of truthful entities, not a filename or a schema trick.
• Put the same claims in the title, H1, body, and schema. Do not invent a second story in llms.txt, structured data, or social bios.
• The work that matters is honest public pages — the site, the copy, and SEO — not a second company written for machines.

Search and answer engines should repeat the same facts.

That is the first thing an "SEO and GEO for small businesses" search should hear. Generative engine optimization is not a new ranking lever. It is whether a cautious machine can extract the same entity a person just read — the name, the offer, the proof, the next step — without reconstructing a cleaner company from slogans, schema, or a file at the root.

People also type answer engine optimization and entity SEO. Same job. A search engine decides which URL to retrieve. An answer engine decides which short claim it can safely repeat. Both should hear one public truth. If they hear two, you taught them a fiction.

What SEO and GEO actually are

SEO is still the retrieval problem. A crawler has to find the page. An index has to understand what the URL is about. A ranking system has to decide whether that URL is useful for a query. Titles, headings, visible copy, internal links, speed, and demand still matter. None of that is new, and none of it is a promise that a page will rank.

GEO — generative engine optimization — is the extractability problem. A chat tool or a generated search answer may name a company, a service, and a fact. It may shrug. It may invent a better version of you from a bio that does not match the homepage. The useful question is not "how do we rank in ChatGPT." The useful question is: if a cautious model quotes us, can it do so from a sentence we already published and will stand behind?

Answer engine optimization is the same discipline under a different acronym. Entity SEO is the same discipline aimed at the nouns: who you are, what you sell, what you do not sell, how someone starts work. The acronyms multiply because vendors need a new product. The work does not.

Three readers. One page. One story.

If the homepage says you design and build websites, the title should not say you are a growth platform. The H1 should not say you are an AI company. The schema should not add a service the visitor cannot find. The llms.txt file should not invent a metric the HTML will not admit. That is GEO when the phrase means anything: extractability of truthful entities, not a metadata trick.

One public truth

A public truth is a claim you will repeat in every place a stranger, a crawler, or a model might look.

For a small business the list is short:

• The legal or trading name, written the same way.
• What you sell, in nouns a buyer uses.
• Who it is for, if that constraint is real.
• How someone starts — a form, a call, a booking.
• The proof you can actually show.
• The founding year, the operating model, the contact route, if you publish them at all.

Write that list once. Then put the same claims in the title, the H1, the body, and the schema. If a claim cannot survive that repetition, it is not ready to publish. It is a slogan.

This is not a style preference. Search snippets are selected algorithmically. They often come from visible page text rather than the meta description you wrote. An answer engine that cites you will lift a short, supported sentence from HTML, or it will skip you. Schema that introduces a claim the visitor cannot read is not "optimization." It is a second story. A second story is how entities get blurred.

One public truth means you refuse to maintain two companies: the one a person sees, and the one you hoped a machine would prefer.

Extractability is the job

A model will not reconstruct your business from "innovative solutions" or "tailored excellence." Those phrases contain no entity. They do not name a service. They do not name a next step. They are easy to write and impossible to quote without making something up.

Extractability looks like ordinary sentences:

• We design and build brands, websites, and digital products.
• The scoped site is designed, written, and launched.
• Project intake is a form. You keep running the business.

Those sentences can be lifted. They can be checked against the page. They can appear in a title without becoming a different company. That is entity SEO for a small business in 2026: make the nouns stable, visible, and boring enough to repeat.

What extractability is not:

• A JSON-LD block that lists services the page never describes.
• A keyword in every heading because a 2012 checklist said so.
• A filename at the root that "adds GEO."
• A social bio that claims a category the site does not support.
• A promise that any of the above will rank you or get you cited.

If a vendor sells generative engine optimization as a pack of hidden fields, they are selling a trick. The trick fails the first time a person lands from search and reads a different business than the one the model described.

The same claims, four places

The cheapest integrity test in search and answer-engine work is alignment.

Title. One document, one subject. The title is packaging for retrieval. It should name the same job the page does. It should not bait a query the body will not answer.

H1. The heading a person sees first should be the same claim as the title, in language a buyer would say out loud. If the title and the H1 disagree, you have already split the entity.

Body. The first screen has to make the fact literal. A memorable headline may be broad. The supporting copy must not be. Prefer concrete nouns: website, offer, form, launch, repair. Cut internal strategy prose. A person should know what you are, who the page is for, and what to do next before they scroll.

Schema. Structured data may clarify a visible fact. It may mark up the organization, the page type, the offer that is already on the page. It may not introduce a service, a review, a price, or a proof the visitor cannot read. If you would be embarrassed to put the claim in the H1, it does not belong in JSON-LD.

Those four places are not a funnel. They are one sentence, restated. When they match, a search engine and an answer engine can do their different jobs on the same truth. When they do not, you have published a contradiction and called it optimization.

The same rule applies to the optional note for agents. What llms.txt is — and what it is not is the longer version: a README, not a ranking lever. Google Search does not use the file. A well-made one matches the public site. A badly made one invents a cleaner company than the HTML will admit. If you write one, write it after the pages exist. Never let it outrank the HTML.

Where a second story gets written

The second story is usually cheaper than the first. That is why it appears.

Schema. A plugin dumps every possible type. LocalBusiness, ProfessionalService, Product, FAQ, Review — whether or not the page shows those things. The visitor sees a five-page offer site. The graph sees a marketplace. An answer engine that trusts the graph over the prose will describe a business that is not there.

llms.txt. Someone hears that agents read a Markdown file at the root and writes a better about-page than the homepage. They add a metric. They add a service. They add a tone the brand does not use. The file is public. A person can open it. If it disagrees with the site, both readers learn you are sloppy.

Social bios. The LinkedIn line says "AI-powered growth." The X bio says "full-service agency." The Google Business Profile, if you have one, says something else again. External surfaces corroborate an entity only when they repeat it. A contradiction across profiles is entity ambiguity. It is not distribution.

Directories and profiles. A listing that uses a different name, a different category, or a contact route the site does not publish is a second company with your URL attached. Fill a profile only when you can complete it truthfully and keep it current. An empty accurate listing is better than a rich invented one.

The page you wrote for machines. A thin URL stuffed with synonyms, hidden in a footer, or generated so a crawler would have "more content." People bounce. Models that quote it quote mush. The ordinary search work is still useful pages, crawlable HTML, and claims you can defend — not a second site for bots.

The pattern is the same in every case. Someone did not want to decide what the business actually is. They wrote a more convenient version in a place they hoped a machine would prefer. Machines compare. People compare faster.

What a small business should make extractable

You do not need a knowledge-graph program. You need a short list of facts that survive contact with a skeptical buyer.

Name. One spelling. One domain. If you trade under a short name, say so on the page that introduces the company. Do not let the title, the logo, and the footer disagree.

Category. What you sell, in the buyer's nouns. "Creative and technical network" is a positioning line. "We design and build websites" is an extractable fact. You can have both. The fact has to be on the page.

Offer. The page should say what happens when someone says yes. A scoped site. Ongoing search work. A form that starts a proposal. If the next step is hidden in a carousel, it is not extractable.

Proof. Only the proof you can show. For CLICK.BLUE the public record is specific: founded in 2014, more than twelve years in operation, more than fifty businesses supported, more than a hundred websites launched. Those numbers appear on the site. They are not invented for schema, for a file, or for this article. If you do not have a number, do not mint one. A named process is better than a fake metric.

Limits. What you do not do is part of the entity. A page that claims every digital job is a page an answer engine cannot safely summarize. Narrow territory is easier to quote because it is easier to check.

Freshness. When the offer changes, change the title, the H1, the body, and the schema in the same week. A current page with last year's service list is a second story with a date stamp.

That list is the GEO loop without the folklore: make the canonical page clear, keep external profiles in agreement, and improve the page when a check shows a missing fact. Monitoring a chat tool does not itself improve visibility. It tells you where the public truth is thin.

Files and schema do not mint a citation

This is the rule that keeps the work honest.

An answer engine may quote a short, supported sentence from visible HTML. It may ignore you. Schema and llms.txt may repeat that sentence. They cannot mint a citation. Anyone who tells you otherwise is selling a file.

Google's published guidance on generative features in Search is blunt about machine-readable extras: you do not need new AI text files or special markup to appear in those features, because Search itself does not use them. A later note adds the practical line: it is fine to maintain llms.txt for other systems. Doing so will not help, and will not harm, visibility in Google Search. Ignores is the verb. Neutral is the outcome. Optional is the status.

Read that as a constraint on the week, not as a ban on the file. If the homepage is still a slogan and the service pages still disagree with each other, the wrong place to spend Monday is a README at the root. The right place is the pages.

The same constraint applies to structured data. Markup that matches the page can help a system understand type and entity. Markup that invents reviews, prices, or services is a trust problem. Search systems have been discarding that class of fiction for years. Answer engines that check sources will discard it too.

So the order of work is not "add GEO, then decorate a site around it." The order is:

1. Decide what the business actually sells. 2. Put that on public pages a stranger can finish. 3. Make those pages crawlable, fast enough, and internally linked. 4. Repeat the same claims in the title, H1, body, and schema. 5. Align the bios and listings you already have. 6. If you want a note for agents, summarize the pages you already shipped.

Skip step six if you have not finished step two. A precise file about a vague site is still a vague site.

When to do this yourself

Do the alignment yourself when most of these are true:

• You can write the offer in one sentence and stand behind it.
• The public pages already agree with each other, or you will make them agree this month.
• You will change the title, H1, body, and schema together when the offer changes.
• You will not publish a number, a service, or a review that the visitor cannot see.
• You want a note for agents only after the HTML is honest.

Skip the metadata project when the homepage is still mush, the offers are still being invented, or someone is asking you to "add GEO" by dropping a file on a site that cannot yet explain itself. In that case the next step is not schema. It is the pages.

If you already know the offer and need the site to say it — and to keep saying it in search — that is a full website and the SEO that follows. If you want to master the discipline yourself, start with the sentence, then the four places, then the bios. Copy the rule. Do not copy anyone else's claims.

The presence is still the expensive part

This is the same fork as the other tools. Webflow is software. A schema plugin is software. llms.txt is a text file. The unfinished presence is the expensive part: the designer, the writer, the marketer, the evenings, the site that does not yet look, read, or retrieve like a business.

CLICK.BLUE is a delivery team for that presence. A project manager scopes the work. Specialists design, write, build, and launch. We have done this since 2014 — more than twelve years, more than fifty businesses, more than a hundred websites. Sometimes the build includes structured data and an llms.txt that match the public site. Those are byproducts of pages we are willing to stand behind. They are not the product.

We do not promise rankings. We do not promise citations. We do not write a second company for machines. We put one public truth on the pages, and we keep it there.

If the site does not yet say the thing, start with the site. If the site says three things, pick one and align the rest. The estimator at get started turns the current setup into a scoped proposal — the site and the search work, not a file for sale.

A filename will not make you extractable. Honest public pages might be found, and might be quoted. That is the work we take.