Output types
Six result classes, kept separate.
A useful label prevents an exact count, an editorial warning, and a live-site observation from looking equally certain.
Exact calculation
A deterministic result from stated inputs and a published formula or count, such as bytes, percentages, character counts, or WCAG contrast ratio.
Deterministic inspection
A repeatable parser or validator reports what it can observe in supplied text, markup, or rules. It does not infer how every browser or search system will behave.
Heuristic guidance
A transparent editorial pattern identifies something worth reviewing. It is a prompt for judgment—not proof of quality or ranking impact.
Visual or statistical approximation
A preview or formula estimates a presentation or reading characteristic that may differ by query, device, language, browser, or live platform behavior.
Planning or readiness check
A checklist confirms that documented questions were considered. Completion does not forecast indexing, traffic, citations, accessibility, or business results.
Bounded live inspection
A disclosed server-side request inspects a limited public target and returns observable evidence. Its page limit, timeout, failure states, and safety controls are part of the result.
Sources
Primary documentation comes first.
Time-sensitive rules are checked against the platform or standards body that owns them. A third-party study may add context, but it should not silently replace an official specification or product document. Source-backed pages show a review date so readers can judge freshness.
- Google: optimizing for generative AI featuresGenerative-search eligibility, content practices, measurement, and mythbusting
- Google: title links in search resultsHow title links may be selected, rewritten, and displayed
- Google: snippets and meta descriptionsHow result descriptions may be created and truncated
- Google: URL structure best practicesReadable, crawlable, and maintainable URL guidance
- W3C: Web Content Accessibility Guidelines 2.2Accessibility requirements, contrast formulas, thresholds, scope, and exceptions
- Bing: AI Performance in Webmaster ToolsCitation reporting, reported dimensions, and interpretation limits
Processing boundaries
Local by default, with exceptions disclosed where they occur.
Most Plainview tools process entered text, rules, and image files in the browser tab. A tool that needs a network request must explain the destination, purpose, and data boundary beside the relevant control.
Browser-local work
Inputs usually stay in the tab.
Text checks, calculations, previews, and supported image transformations run locally unless the individual tool says otherwise. Reloading normally clears unsaved work.
Optional public-site crawl
Internal Link Suggestion can request a bounded live inspection.
Its local inventory mode stays in the browser. Its separate live mode sends the supplied public URL to Plainview's server, which follows documented limits and returns page evidence rather than unrestricted crawling.
Review the tool boundarySelected font request
Google-labeled fonts load from Google when selected.
The Font Pairing Previewer serves its starter set from Plainview. Choosing a family labeled Google requests that font family and weight from Google; the editable sample text is not part of the font request.
Review font behaviorOptional Google Analytics does not receive tool-field values. It may measure normal page and defined interaction data only after consent. See the privacy and terms page for the current site-wide disclosure.
Maintenance
A visible review date is part of the result.
Source-backed guidance is reviewed during migration, when a material source or platform behavior changes, and during planned maintenance reviews. Material changes should update the tool, related guide, tests, and visible date together. Plainview does not claim a fixed review cadence that has not been operationally established.
- 01Identify the authority
Use the current specification or first-party platform document for the rule.
- 02Encode the boundary
Make assumptions, formulas, exclusions, and failure states visible in the interface.
- 03Test the contract
Verify helpers, server-rendered explanation, accessibility, privacy claims, and representative edge cases.
- 04Record the review
Change the date only when the source-backed behavior and its claims have actually been reviewed.