FUNNEL PAGE TITLE AND DESCRIPTION WORKSHEET Companion: Plan page titles and descriptions that match your funnel Purpose: prepare factual text for one intended page and keep the proposal separate from saved-page evidence and an observed Google result. This is a planning record, not an implemented CFAI setting, indexing request, ranking test or publication. Do not change access, robots, redirects or canonical settings to complete this worksheet. No live page or search check was performed for the fictional examples below. Every implementation/search result is NOT RUN. 1. PAGE AND FACT REGISTER — COPY FOR EACH REAL PAGE Record ID: Project / intended product: Exact intended URL or planned path: Environment (planned / preview / public / unknown): Page's single visitor task: Audience and supported service area, if relevant: What the page actually contains: What happens after the page's action: Important limitation: Fact source (approved brief or exact current page/section): Source checked date / person: Fact owner: Unsupported or unresolved claim: Question for that owner: Proposed document title (): Proposed visible main heading: Proposed meta description: Why this differs from the nearest related page: Copy decision (PROPOSED / APPROVED FOR IMPLEMENTATION / HOLD): Reviewer / decision date / reason: Do not use a character target as a guarantee of display or ranking. Keep the distinguishing facts understandable even if the display is shortened. The main heading and title may differ while describing the same page task. 2. FICTIONAL FILLED RECORDS — ORIGINAL PLANNING EXAMPLES Cedar Garden Studio and its page facts are invented. They establish no real service, geographic availability, customer outcome or product capability. M01 — Service-enquiry page Planned path: /garden-design-enquiry Task: Ask about a residential garden-design project in Riverton. Assumed page: Service explanation plus an enquiry for a person to review. Limitation: No confirmed appointment and no instant price. Rejected title: Best Garden Design — Free Instant Booking Reason: Best/free/instant booking are unsupported by the fictional brief. Title: Garden design enquiries in Riverton — Cedar Garden Studio Heading: Ask about your garden-design project Description: Planning a residential garden in Riverton? Read about Cedar Garden Studio's design service and send an enquiry for the team to review. Owner question: Are service area, service text and enquiry next step all correct? Decision: PROPOSED, awaiting factual review in a real use. Saved-page result: NOT RUN Search-result observation: NOT RUN M02 — Preparation guide Planned path: /garden-consultation-preparation Task: Gather photos, priorities and questions before a conversation. Assumed page: On-page checklist; no enquiry form or consultation reservation. Title: Prepare for a garden-design conversation — Cedar Garden Studio Heading: What to gather before discussing your garden Description: Use a checklist of garden photos, priorities and questions to prepare for a design conversation. Read the preparation guide on this page. Distinction: Preparation here; sending an enquiry belongs to M01. Decision: PROPOSED, awaiting factual review in a real use. Saved-page result: NOT RUN Search-result observation: NOT RUN M03 — Unsupported location-page proposal Proposed path: /lakeside-garden-design Unapproved title idea: Garden design in Lakeside — Cedar Garden Studio Available fact: Only Riverton is confirmed in the fictional brief. Missing: Approved Lakeside service area and distinct page content. Title / heading / description decision: HOLD Owner question: Is Lakeside served, and what would this page actually provide? Next action: Resolve those facts before preparing the three fields. Saved-page result: NOT RUN Search-result observation: NOT RUN 3. SAVED-PAGE CHECK — ONLY AFTER AUTHORIZED IMPLEMENTATION Record ID / implementation owner: Exact URL and environment checked: Check time and timezone: Actual document title: Actual visible main heading: Actual meta description, absent or unknown: Evidence reference: Do the stored facts/text match the intended page?: Difference / unresolved fact / next owner: Status: NOT RUN (replace only with an actual observation) A preview check is not evidence of publication or search display. This worksheet does not establish which settings a particular builder provides. 4. SEARCH OBSERVATION — SEPARATE FROM WHAT YOU WROTE Record ID: Exact query: Observation date/time/timezone: Device/display context: Search surface: Intended page URL: Returned page URL, or not observed for this query: Displayed title link: Displayed snippet: Evidence reference: Difference from proposed/saved text: Next question / owner: Status: NOT RUN (replace only after an actual observation) Different displayed text does not by itself prove a broken setting. Not observing a page for one query does not establish index exclusion. Do not infer more clicks, rank improvement or enquiries from a copy change or a single observation. 5. REVIEW BEFORE HANDOFF [ ] One exact page and one task are identified. [ ] Each factual claim has a source and owner. [ ] Title, heading and description describe that same task. [ ] Related pages are distinguished by what they actually provide. [ ] Unsupported best/free/instant/location claims are removed or on HOLD. [ ] Proposed, saved-page and observed-search records remain separate. [ ] Unperformed checks remain NOT RUN. [ ] Current access and publication gates remain unchanged. Sources (guidance, not actual results): https://developers.google.com/search/docs/appearance/title-link https://developers.google.com/search/docs/appearance/snippet