Why do we write the exact kind of page we would close as a buyer? When we are buying, we want to know what is included, whether it fits our situation, and what happens next.
Yet give us a blank document, and suddenly we are “committed to delivering exceptional solutions.” Apparently, opening the CMS deletes our memory.
The mistake can start before the first sentence. We ask what the page should say before deciding what it must answer. Then the buyer has to find the offer, interpret the promises, and guess how the service works.
I use eight rules to make those answers clear. I call the writing system Frame-Net Doctrine. It connects the buyer's question to a section and the section's claims to evidence.

Day 5 explained the entity model: what the business offers, who it serves, and how those things connect. The writing must keep those relationships clear. A defined service cannot turn into “passion for excellence” as soon as we open a document. Read Day 5: Entity-Based SEO.
A money page helps someone make a buying decision. It might sell a product, explain a service, or introduce the business and direct a visitor to the right offer. Its job is to help the reader decide what to do next.
Start With How the Business Serves Its Market
Before I choose a template, I check who can receive the offer and where. A service delivered from one branch needs different information from software available to users in several countries.
Here, “business model” means the business's relationship to its market. It tells me what the page must explain about availability, fit, and delivery. Pricing methods, such as subscriptions or hourly billing, come later.
I use five operating contexts. Each gives the writer a different starting question.
| Operating context | What the page must make clear |
|---|---|
| Local business with one location | What it offers, where it works, and how to book |
| Local business with several locations | Which branch serves the reader and what that branch offers |
| Business serving several countries | Where the offer is available and which conditions change by country |
| Ecommerce seller or manufacturer | What the item includes, which variants are available, and how it reaches the buyer |
| Software without a location-dependent offer | Who it suits, what it does, and which plan or integration limits apply |
A city name tells the reader where a local service is available. It does not explain what the service includes. A head-office address also does not prove that every branch offers the same work.
For software, “for distributed teams” may be a more useful qualifier than a city. The page then needs to explain the shared workflow, supported inputs, and limits. I choose the qualifier that helps the reader judge the offer.
Choose the Template for the Page's Job
The business context tells me who can buy. The page type tells me which decision this URL should help them make. A homepage introduces the business; a service page explains one job the business can perform.
I use six commercial page types when choosing a template. They are categories in my system, rather than a rule that every website must have exactly six kinds of page.
| Page type | Reader's main question | What the template needs |
|---|---|---|
| Homepage | What does this business offer? | Identity, main offers, proof, and routes into the site |
| Industry or vertical | Does this suit my kind of business? | Audience needs, relevant capabilities, and evidence |
| Location | Can this business serve me here? | Local availability, scope, proof, and contact details |
| Service or sub-service | Should I hire this business for this job? | Scope, fit, process, cost factors, and booking |
| Product | Should I buy this item or plan? | Specifications, compatibility, options, price, and terms |
| Collection | Which item should I choose? | Inventory, comparison details, filters, and buying guidance |
A local service page combines a service with its market. It needs to explain both, while keeping the focus on that service. Adding every other offer from the company would change the page's job.
A software feature page can use product-page logic to explain one capability and its limits. A software use-case page can use industry-page logic to explain who that capability suits. I choose the template by the decision, even when the site's page labels differ.
The tool also handles supporting material such as company information and policies. It calls this an operational brand-authority type. Those pages support the offer without becoming a seventh commercial category in this article.
Rule 1: Main Context First
Answer the immediate question before introducing the business's values. A reader should know what the offer does without searching through the opening.
Compare “We turn your vision into reality” with this illustrative opening: “The scheduling app assigns shifts, records availability, and alerts managers to uncovered hours.” The revised sentence names the product and explains three capabilities. A real page can use that sentence only if the app supports them.
The same rule applies under each heading. A delivery section should open with delivery information, and a plan section should open with what the plan includes. I read the heading and opening sentence together to check whether they answer the same question.
Rule 2: Noun-Verb Connection
Name who does the work and what they do. “Our commitment to quality forms the foundation of our excellence” gives the reader no action to inspect.
“The account manager records the scope before the customer approves the proposal” is clearer. The account manager acts, the scope is recorded, and the customer approves it. The sentence also explains when approval happens.
This makes review easier because I can identify the actor, action, and condition. It also makes the relationship easier to record as structured information. That is a writing benefit, not a promise that a search system will rank or cite the sentence.
Rule 3: Affirmative Structure
State the actual condition. Replace “You will not be left guessing about delivery” with information the buyer can use.
For example, a verified purchase process might support: “The checkout shows the delivery charge and estimated dispatch date before payment.” The reader now knows what appears and when. An editor can check both details.
Keep real exclusions clear. “This plan does not include telephone support” helps a buyer decide whether the plan fits. Affirmative writing removes vague reassurance; it does not remove useful negative facts.
Rule 4: Chronology
Explain events in the order they happen. Approval should appear before the work it authorizes, and verification should follow the work being checked.
Compare “We deliver the project, discuss your requirements, and prepare a proposal” with “The team records your requirements, prepares the proposal, and schedules the approved work.” The revised sentence lets the reader follow the process. It also shows which decision controls the next step.
A longer process can follow the same logic: requirements, scope approval, delivery, verification, and handoff. Each step needs a reason to follow the previous one. I check those dependencies before polishing the wording.
Rule 5: No Fluff
Keep sentences that add useful information. A sentence can explain an inclusion, a limit, a condition, a reason, or a next step.
“Our experienced team delivers exceptional results” gives the buyer little to assess. “One project manager coordinates the approved scope and customer updates” names a role and its responsibility. That replacement still needs business evidence.
A true sentence can also become fluff through repetition. Three paragraphs repeating the same service and city have not explained three new things. I establish the context once, then use the next sentence to add detail.
Rule 6: Clarity Before Selling
Explain the offer so the buyer can evaluate the sales claim. Scope, fit, and delivery give that claim meaning.
I use five modes to describe a section's purpose: Identification, Suitability, Function, Incentive, and Post-Purchase. In plain language, they ask what the offer is, who it suits, how it works, why to choose it, and what follows the purchase. A process section explains Function; a supported warranty explains Post-Purchase conditions.
The tool's numbered funnel stages do a different job. They arrange sections in a suitable reading order for the page type. The five modes describe meaning; the stage numbers describe placement.
A ready buyer can still use a button near the opening. “Book a consultation” or “Compare plans” names that action clearly. This rule asks the explanation to support the sale, rather than asking every visitor to read the whole page before acting.
Rule 7: Brand-Name Weaving
Name the business when stating a promise it owns. A paragraph full of “we” may lose that connection when someone reads it on its own.
“[Brand] includes onboarding in the annual plan” identifies who owns the policy. The real page needs the actual business name and a verified inclusion. Once the subject is clear, a pronoun can continue the thought.
I use this rule to separate general information from company promises. A general cost explanation describes the category. A payment policy describes what this business has agreed to do.
Rule 8: Take the Frame, Not the Wording
Use a reference to identify useful questions. Then check where those questions belong and answer them from the evidence available for this page.
I use query-demand analysis, or QDA, to group those questions. Cost questions belong together; compatibility questions form another group. Inside compatibility, supported operating systems and file formats may be separate details.
The answer determines the format. A supported-device question might need a list, while a configuration question might need its own explanation. Search volume can help prioritize those questions, but it cannot tell me what a product supports.
A competitor's heading is a prompt to investigate. It does not prove that our page needs the same heading or can make the same claim. I keep the useful question and write the answer from our own inputs.
What Breaks When a Rule Is Missing
Each rule addresses a different writing failure. Direct copy can still contain an invented promise, and accurate copy can still put the process in the wrong order.
| Rule | What the reader loses | What I inspect |
|---|---|---|
| Main Context First | A quick answer | Does the opening answer its heading? |
| Noun-Verb Connection | A clear explanation of the work | Can I identify who does what? |
| Affirmative Structure | Usable conditions | Does the sentence state a supported fact? |
| Chronology | A process they can follow | Does each event follow its prerequisite? |
| No Fluff | Attention spent on useful detail | Does the sentence add information? |
| Clarity Before Selling | Enough context to judge the offer | Has the page explained the value it asks them to choose? |
| Brand-Name Weaving | Ownership of the promise | Is it clear which business makes the claim? |
| Take the Frame, Not the Wording | Coverage that fits this page | Does the question belong here, and can we answer it? |
These checks explain what needs repair. They do not give a page a guaranteed ranking, citation, or conversion rate. I use them to judge the quality of the explanation.
How the Tool Applies the Rules
The tool needs to settle three questions before it writes: which sections belong, what each section must answer, and which evidence it may use. The outline answers the first question. The section instructions and supplied facts answer the other two.
I supply the business analysis, query information, template, and target page. I include the relevant workbook tabs because a summary can miss a policy or exclusion recorded elsewhere. A writer cannot preserve a condition it never receives.
Give the Tool a Clear Page and Template
I identify the subject, audience, business role, and intended action. Selling delivery and teaching someone to do the work are different purposes. Sharing a topic does not make those pages interchangeable.

The intake separates analysis, templates, and voice instructions. Business analysis supplies company facts, and the template supplies the structure. Voice instructions change how the page sounds.
The tool can generate an outline from the page context and QDA. It can also work from an authored template. Both routes must give the writer clear instructions for each section.
A suitable authored template keeps its heading levels and order while the tool assigns stages and facts. An unrelated template needs review before writing continues. If the template fails to load, I fix that input rather than treating the missing structure as permission to improvise.
Decide What Each Section Does
The tool reads the topic, its context group, and its writing instructions. It then assigns a section role, such as process, cost, coverage, or reasons to choose. That role is also called a section key in the engine.
The role informs four decisions. Together, they tell the next stage how to handle the row.
| Decision | Plain meaning | Example |
|---|---|---|
| Funnel stage | Where the section goes | Process sits with delivery information |
| Authority class | Which evidence guides it | Reasons to choose need company evidence |
| Structural treatment | How its children appear | Process steps form an ordered list |
| Prose responsibility | Whether it needs a paragraph | A gallery may need assets and captions instead |
A section can receive the wrong role or no role. The classifier leaves the key empty when it finds no matching pattern. I review those rows before relying on their later assignments.

The supplied review screen contains notes whose subject differs from the selected job label. That mismatch tells me to inspect the saved checkpoint. The image does not show whether those notes still apply or whether the issue has been corrected.
Separate General Knowledge From Company Evidence
The tool uses two authority classes: service-weighted and business-weighted. A service-weighted section explains the category, such as factors that affect scope. A business-weighted section explains the provider's own policies, proof, or practices.
Market research can identify useful questions about a service. It cannot establish this company's payment schedule or coverage. Those answers must come from the business.
| Section | Class | Evidence needed |
|---|---|---|
| Service inclusions | Service-weighted | Category coverage plus the company's actual scope |
| Cost factors | Service-weighted | Sourced general context; company figures need company records |
| Reasons to choose | Business-weighted | Verified company differences and proof |
| Areas served | Business-weighted | Approved coverage information |
| Reviews and gallery | Business-weighted | Authentic reviews and approved project assets |
The routing model has no third “mixed” class. A cost section can contain general information and a company policy. Each statement still needs its own source, even though the section has one research route.
Put Each Fact Where It Helps
Fact hosting means assigning a fact to a suitable section. For example, a support channel belongs with support, annual billing belongs with pricing, and a cancellation condition belongs with terms.
I check for gaps in both directions. A supplied fact with nowhere to go may reveal a missing section. A warranty heading with no warranty information reveals a missing claim input.
An assigned fact is available to the writer. It is not an order to repeat that fact everywhere it could fit. The section instructions decide which part the writer must use.
Use Location for a Clear Reason
Location has three jobs: naming the market, listing coverage, and explaining a relevant local condition. I keep those jobs distinct so a place name adds meaning.
The opening can name the market. An areas-served section can list approved locations. A verified delivery restriction can appear where it affects delivery.
A city mention alone does not establish local expertise. That needs a relevant fact, such as a supported availability condition. Repeating the city cannot supply the missing evidence.
Preserve Facts and Exclusions
Company claims start with verified company information. General research can explain the wider issue, but it cannot fill a gap in the company's records.
I apply three steps when checking a claim. Each step keeps the source's meaning intact.
- Use the verified company value with its conditions.
- Use sourced general information for a general question and make its source clear.
- Omit the unsupported claim or record the missing input for the editor.
A company founded in 2018 cannot become a company with “25 years in business.” Combined team experience is a different fact with a different subject. I can use it only if the records support that meaning.
An exclusion is also a fact. “No telephone support” answers a plan question; a blank support field does not answer it. I preserve that difference.
Arrange Sections in a Useful Order
Funnel staging places sections in the order that suits the buying decision. A local service page may move through need, scope, delivery, cost, evaluation, and action.
Query demand can help order questions within a stage. It should not move pricing ahead of all context just because a cost query is popular. When the tool arranges a generated outline, it keeps each parent section with its children.
The opening can change by page type. A core service or industry page may start with trust and define the offer. A local service variation can start with the need because the reader already names the service and market.
A suitable authored template keeps its deliberate structure while the tool checks it. The tool does not automatically sort every outline in the same way. I check which route produced the outline before reviewing its order.
Specify the Answer the Opening Must Give
An answer contract tells the writer how to answer the heading. I review that instruction before writing. The tool can infer a missing type from the wording, but that inference still needs checking.
The engine uses names such as definitive, grouper, and boolean. They mean a direct statement, a set of values, and a yes-or-no answer with conditions. The names are useful once the actual answer is clear.
| Heading | Answer type | What the opening needs |
|---|---|---|
| Which file formats can it export? | Grouper | The supported formats |
| What does the account manager do? | Definitive | The role and its responsibilities |
| Does this plan include telephone support? | Boolean | The verified verdict and any condition |
I also define where the section stops. A support section can cover channels and availability. It does not need to explain the whole onboarding process.
Use Lists When the Items Are the Answer
CSV, PDF, and XLSX can form a list of supported formats. They do not each need a heading and a paragraph if the format name answers the question.
An item needs more space when it carries a separate question. A format with its own configuration requirements may need a subsection. I let the information determine the structure.
Some parent headings need no body paragraph. A gallery can contain images and captions, while an FAQ heading can contain its questions and answers. I add prose when it helps explain something those elements do not already answer.
Let the Required Answers Determine the Length
An obligation is something a section must explain. A delivery section might need to cover destinations, charges, dispatch timing, tracking, and exceptions. Those five answers tell the writer what completion looks like.
A short paragraph and a list may cover them. An extra paragraph about commitment does not answer a sixth delivery question. I judge length by missing or repeated information.
Required answers
What does this section still need to answer?
Select an answer to see the fact behind it. Remove that fact to see what the writer can no longer claim.
A count of declared answers — not an SEO score, an AI confidence score, or publication approval.
Select an answer
Shipping & delivery section
Example Store ships within the 48 contiguous US states. Standard shipping costs $6 per order, and orders dispatch within two business days after payment is confirmed. The dispatch email includes a tracking link. Delivery to PO boxes is unavailable.
When will the order dispatch?
- F03 · input
- Orders dispatch within two business days after payment is confirmed.
- In the passage
- “Standard shipping costs $6 per order, and orders dispatch within two business days after payment is confirmed.”
- Why it answers
- This answers when the order leaves the store. It preserves the condition that payment must be confirmed.
The internal quality baseline examined nine human-written commercial pages. Its length table covers 403 non-empty headed sections and excludes list items from prose counts. The figures describe that sample.
| Heading level | Median prose length |
|---|---|
| H1 | 182 words |
| H2 | 100 words |
| H3 | 81 words |
| H4 | 65 words |
The same baseline found that 32% of H2s had no body prose. It also found that 73% of list items were short labels. Those observations explain why every heading does not need an introduction.
They are not word targets. A section is too thin when it leaves a required question unanswered, and too long when it repeats an answer. The word counter can count either version, although it is remarkably willing to supervise the meeting.
Worked Example: Bathroom Remodeling Dallas
Here is the method applied to Bathroom Remodeling Dallas. I use North Dallas Renovations as a demonstration name and give it a fictional set of business facts. This is a teaching example composed from those inputs.
The example uses declared service details rather than live query research. Search volumes remain unknown. That lets us inspect the writing method without treating the demonstration as market evidence.
Set the Page's Purpose and Inputs
The page serves Dallas homeowners planning a bathroom remodel. Its next step is a consultation request. Kitchen work, whole-home work, and emergency plumbing sit outside this page's scope.
I record the demonstration facts before writing. Each fact has an ID in the specimen so the finished statements can be checked against it.
| Input | Fictional value |
|---|---|
| Offer | Residential bathroom remodeling in Dallas |
| Scope | Layout, shower and tub work, vanities, storage, tile, lighting, ventilation, fixtures, and finishing |
| Typical price range | $18,000 to $45,000, depending on scope — a typical range, not a fixed quote |
| Starting point | Consultation and an on-site review |
| Proposal | Written scope, selected allowances, payment schedule, and exclusions |
| Changes | Written change order with the scope and price effect |
| Coordination and handoff | Assigned project manager, final walkthrough, and punch-list record |
The inputs supply no warranty, financing, reviews, credentials, or project duration. I leave those claims out. A writer cannot replace missing proof with confident adjectives.
Decide What the Cost Section Must Explain
The cost section is service-weighted because it answers a general pricing question. Company terms still come from the fictional business facts. The business supplies a typical price range rather than a single fixed quote, so the section can give a direct answer without promising a number it has not measured for the specific project.

The saved brief shows fields for heading level, order, stage, answer format, and writing instructions. Its 71 rows belong to that home-remodeling sample. They are neither a recommended length nor the row count of this bathroom example.
I give the bathroom cost section five obligations. Each one names an answer and the input allowed to support it.
| Required answer | Input | Writing limit |
|---|---|---|
| The typical price range for a bathroom remodel | Fictional fact BF-16 | Give the stated range as typical; no fixed quote for a project not yet reviewed |
| What moves a project within that range | Teaching input SC-03 | No claim about measured Dallas demand |
| What the written proposal contains | BF-04 and BF-05 | Keep allowances, payment schedule, and exclusions |
| What happens when approved work changes | BF-06 | Keep the written scope and price condition |
| How newly exposed conditions affect the plan | SC-04 | No promised contingency price or outcome |
The section answers pricing and explains the proposal. It does not need to repeat the full construction process. That process has its own place in the outline.
Write From Those Answers
Here is the passage for “How Much Does Bathroom Remodeling Cost in Dallas?” Its business statements use the fictional facts, and its general explanation uses the declared teaching inputs.
Most bathroom remodels with North Dallas Renovations fall between $18,000 and $45,000, depending on the planned scope, room size, layout changes, selected fixtures, surface area, and required trade work. That is a typical range, not a fixed quote. The team prepares a written proposal after reviewing the existing bathroom and agreeing the proposed work.
The proposal records the scope, selected allowances, payment schedule, and exclusions. A requested change or newly exposed condition may alter the approved work. Before that changed work proceeds, a written change order records its scope and price effect.
The opening answers the cost question directly with the business's stated range, then names what moves a project within it. The next sentences explain how the written proposal fixes the price and how changes are recorded. The range is given as typical and drawn from the business's own figures, not invented to fill the section, and no fixed quote is promised before a review. The section stops once it has explained its required answers.
Check the Copy Against the Inputs
I now read the passage in reverse: from each statement back to its supporting input. This catches a promise that sounds reasonable but never appeared in the facts.

The saved editor contains verification markers. Those claims need to be resolved or removed before publication. Being in the final-content tab does not make the copy approved.
The bathroom passage covers the typical price range, cost factors, proposal contents, and the change condition. It adds no fixed quote, warranty, or completion promise. That gives the reviewer a specific way to judge whether the section is finished.
Give the Writer and Builder the Same Plan
A heading list does not tell a writer which facts to use. It also does not tell a designer where proof belongs or a builder where a link should lead.
I use three tabs to carry those decisions: Context Breakdown, Content Outline, and Signal Elements. The larger export package can include more sheets. These three keep the main responsibilities clear.
Keep Context, Outline, and Page Signals Together
Context Breakdown records the subject, business purpose, intent, required attributes, and query information. For a product, it distinguishes the item from the seller and intended user. The writer can then explain how they relate.
Content Outline turns those inputs into headings and instructions. Each row can include its level, topic, method, useful vocabulary, and internal-link destination. The enriched brief adds the section purpose and required opening answer.
Signal Elements holds the page title and description. I check them against the finished copy. A title promising a price guide needs a page that actually supplies pricing guidance.

The export keeps the copy and supporting sheets available separately. A reviewer can inspect the brief, QDA, or outline without guessing from the finished paragraph. This helps identify which decision needs changing.
Let Questions Determine Heading Levels
QDA separates major questions from the details that answer them. Pricing can be a major section, usage limits a smaller part of pricing, and a particular overage charge a narrower question. The heading level shows that relationship.
I use this hierarchy when building the outline. A list item stays a list item unless it needs its own answer.
- H1: The whole page's commercial subject, such as a product and its intended user.
- H2: A major decision about it, such as scope, process, or cost.
- H3: A smaller question within that decision, such as usage limits under pricing.
- H4: A narrower question that needs a separate answer within its H3.
- List item: A value, step, criterion, or component.
- Paragraph label: A label that organizes details without introducing a new section.
A coverage list does not need a heading for every place when the answer stays the same. A separate local section earns its space when a relevant condition changes. That difference still needs evidence.
Research the Missing Answer
The research stage checks whether the section needs outside information. Company sections normally need company inputs, while a gallery container needs assets. Neither automatically needs a general research summary.
An operator can override the normal research decision. I review that instruction so the tool does not collect material the section cannot use. The request should identify the missing answer.
The research query also needs the right scope. In the documented route, market location is passed as a search parameter. The query names the question and adds only enough parent context to make it clear.
The Fact Finder handles required hard data that earlier research did not supply. Its evidence policy uses approved tier-one and tier-two source lists. Inclusion on a source list does not remove the need to check whether the source supports the statement.
If the answer remains unavailable, I record the gap. An industry article about cancellation cannot establish our company's cancellation policy. That needs business information before the writer can state it.
Connect the Content to Five Layout Blocks
The money-page skeleton uses five blocks. They organize what the reader sees, while the heading hierarchy organizes the explanations inside them.
| Block | What it helps the reader do |
|---|---|
| Offer and opening action | Identify the offer and take the primary step |
| Need and suitability | Check whether the offer fits their situation |
| Capability | Understand the work, delivery, and relevant options |
| Evidence and operating terms | Evaluate the proof and supported conditions |
| Final contact action | Enquire or buy, with a clear explanation of what follows |
An action can appear where the reader has enough context to use it. A comparison link and a consultation button serve different needs. Their labels should make that difference clear.
The layout must also preserve the heading order. A small visual style does not turn an H2 into an H4. I check the actual heading tags as well as their appearance.
Build Ecommerce From the Product Data
For ecommerce, I decide what the page needs before choosing its layout. The inclusion template identifies elements such as specifications, variants, reviews, product cards, and delivery terms.
The layout template places those elements. The creation procedure then maps attributes and prepares the outline and copy. This sequence keeps the writing connected to the inventory.
A product page explains one item. A collection page helps compare several items. A laptop collection might compare screen size, memory, and operating system when its inventory contains those differences.
A filter adds little when every item has the same value. The selected variant, specification table, and description must also agree. I use the product record as their shared source.
Check Whether the Design Carries the Answers
Before implementation, I check whether the design can display the approved content. The ecommerce reference system lists 14 homepage components, including the hero, collection routes, proof, and resources. A page uses the components its job needs.
I apply four design checks. Each connects a content decision to something visible or usable.
- Decision order: The layout preserves the approved reading sequence.
- Content shape: Tables remain usable comparisons, and process steps remain ordered.
- Evidence ownership: Reviews, project images, and credentials belong to the correct business.
- Transaction path: Buttons, forms, product options, and mobile layouts support the promised action.
The designer now has a plan to build from. The writer also knows which conditions must remain visible. Neither needs to invent a promise to fill a card or remove a condition to fit a slogan.
Audit an Existing Money Page in Five Passes
An audit works back from the finished page to its purpose and inputs. I check the plan, the claims, the answers, and the built experience.
- Check the context and opening. Confirm what the page offers, who it serves, and what action it supports. Compare those answers with the brief.
- Check the section map. Identify each heading's question, evidence class, answer type, and position. Look for missing questions and repeated jobs.
- Trace the claims. Match company statements to company records. Keep general context attributed and resolve missing or contradictory facts.
- Read the answers. Check direct openings, clear actions, and fulfilled obligations. Remove sentences that repeat an answer.
- Check the built page. Inspect headings, assets, tables, lists, links, and actions on desktop and mobile. Recheck anything affected by a correction.
A finding should explain the repair. “The proposal section omits the exclusions in the business record” tells the writer what to change. “Make it engaging” does not identify the missing answer.
Give Each Reviewer a Clear Job
The team lead checks whether the page's decisions make sense. The executor checks whether the copy and implementation carry them out.
| Reviewer | Main responsibility | Evidence to inspect |
|---|---|---|
| Team lead | Correct page purpose and template | Approved subject, audience, intent, and page type |
| Team lead | Necessary sections and suitable sources | Section map, QDA, and fact assignments |
| Team lead | Supported company claims | Business records and approved outside context |
| Executor | Direct, complete answers | Heading, instructions, and required answers |
| Executor | Clear wording and attribution | Sentences compared with their evidence |
| Executor | Working implementation | Rendered page, assets, links, and actions |
The Money Page Audit Checklist (PDF) records checks, findings, owners, and the release decision. It gives each correction a place to be tracked. An unsupported claim remains unresolved even when the surrounding copy reads well.
Use the Audit Screen for Outside Content
The tool can audit content written elsewhere. The screen accepts a document or pasted copy, market information, and selected audit aspects or phases.

This screenshot shows the audit input screen. It does not show a completed result. A report still needs someone to review its evidence and proposed repairs.
Use the Log to Find the Source of a Problem
The log helps locate where a problem began. A missing answer may come from the brief, while an irrelevant section may come from the outline. A failed evidence request may explain an unresolved claim.

The log image shows 99 nodes and 26 signal elements. The separate brief image shows 71 rows and zero signals. The screenshots do not establish that those counters belong to the same checkpoint, so I keep them separate.
Once I find the responsible decision, I correct it and inspect the affected output. Rewriting the paragraph alone will not fix a brief that keeps asking the wrong question. The log makes that upstream check possible.
Carry the Analysis Into the Writing
The eight rules make the explanation clear. The template defines the sections, the tool passes their instructions and facts, and the audit checks the result.
The system still needs a real offer and real evidence. It can explain what the business supplies and identify missing information. It cannot create a service or a review the company does not have.
Day 9 moves upstream into Domain-Wide Analysis. It asks which subjects the website should represent, which pages should exist, and which facts belong to each page. With those decisions settled, the writer can answer the buyer instead of reopening the company's identity in every paragraph.




