For businesses building or rebuilding
Build the intelligence before you build the website.
Why does this need to happen first?
We start before the sitemap. Structure, content and evidence decisions made during a build are expensive to reverse afterwards. They are cheap to settle while they are still decisions.
This is a situation, not a product. It leads into the Pre-Build scope of Goldeneye Check.
What usually happens
Most sites are built, then made discoverable.
The order is backwards, and it is the order that costs money. Four patterns show up again and again.
A page should have a reason to exist. Structured data follows the content model.
A page should not exist because a competitor has one, because the template includes it, because a keyword list suggested it, or because an AI tool generated an outline. It can exist to support a customer decision, an entity, a service, a location, an important question, evidence, a relationship between information, or a next step. The reason should be defensible.
Structured data is not something pasted onto a finished site as an optimization trick. It should describe the real entities, relationships and visible information the content architecture already establishes. It does not cause rankings, citations or AI recommendations.
- 01
The structure is set by the design, not by the decisions
Pages are grouped the way the brand story reads, so the questions customers actually ask have nowhere to land.
- 02
Content is written to fill a template
Copy is produced for sections that already exist rather than for the decisions customers are trying to make.
- 03
Evidence is treated as a launch task
Profiles, records and third-party sources are tidied at the end, long after the systems that read them formed a view.
- 04
There is no starting position
Nothing was recorded before launch, so nobody can say afterwards whether anything actually moved.
What has to be established
Five things a new presence has to satisfy.
The architecture, content and evidence requirements the new presence has to satisfy, established before design and development lock those decisions in.
A website architecture should be informed by what the organization is, what it offers, the entities it involves, the relationships between services and locations, the decisions customers are making, search demand, conversational intent, the content those decisions require, technical accessibility, structured data requirements, measurement requirements, and the evidence and retesting needed later. Goldeneye is defining that intelligence architecture, not designing or building the site.
- The decisions customers are making in your market, and the questions those decisions produce
- Where competitors already hold those conversations, and on what evidence
- The structure the new presence needs so each decision has somewhere to land
- The evidence, records and third-party sources that will need to exist at launch
- A recorded pre-launch position, so movement after launch can be read rather than assumed
A worked example
A new boutique hotel on Fort Myers Beach.
The build brief says twelve pages: home, rooms, amenities, dining, gallery, contact. The decision customers are making is different. They are asking whether a family with a toddler and a dog can walk to a calm stretch of beach in March, and whether parking is included.
Nothing in the brief answers that, so nothing on the new site would either. The competitors already being recommended answer it in a paragraph on a page that does not exist in the template.
What the Pre-Build Check changes
- The page set is derived from the decisions, so each real question has somewhere to land.
- Content requirements are written per page, against the question they answer.
- The records and third-party sources that will need to agree at launch are named.
- A pre-launch position is recorded, so the first months after launch can be read.
Common questions
Before you brief a build.
- What should we decide before a new website is built?
- What customers are actually deciding in your market, the questions those decisions produce, where those conversations are answered today, the structure needed so every decision has somewhere to land, and the evidence that has to exist at launch.
- Why not wait until after launch?
- After launch, structure and content decisions are already paid for. Changing them means rebuilding rather than specifying. The evidence a new site needs, including third-party records, also takes time to be reflected, so starting at launch delays the result rather than the work.
- Does Goldeneye build the website?
- No. Goldeneye establishes the requirements and the baseline, and works alongside whoever builds it, whether that is your internal team, a developer or an agency.
Give the website an intelligence architecture, not just a sitemap.
Where this lands
Pre-Build Check
$3,500 · one-time
This is one scope of Goldeneye Check, not a separate product. The other scope reads a presence that already exists.