Plainview Web

Tool methodology · Reviewed August 26, 2026

How Plainview Tools work.

Learn how the tools calculate results, where their guidance comes from, and what happens to the information you enter. Each tool explains the assumptions and limits that matter for using its output.

Output types

Understand the result you are looking at.

A byte count is a measurement. A search preview is an approximation. Each tool explains how to interpret its output.

Batch and responsive image exports

Image Compressor & Resizer verifies input headers and decoded dimensions, processes one source at a time, then checks each export's actual type and dimensions. Batch and responsive modes never enlarge originals. ZIP files contain completed exports; failed and stopped files are excluded. Responsive markup uses the exported widths and supplied public paths, but does not publish files or verify the destination page's layout. Browser encoding can vary, and the stated file/workload limits are not a guarantee of available device memory.

HTML metadata inspection

Supplied HTML is parsed as inert text to list metadata, resolve declared URLs where possible and check JSON-LD syntax. Findings distinguish repeated values, conflicts and missing context. No page or image is fetched, scripts are not executed, and HTTP headers, rendered changes, indexing and social caches need separate checks.

Website project planning

A project plan records the goals, page inventory and launch decisions you supply. JSON preserves an editable plan; Markdown and CSV support review and handoff. The tool does not research a business, estimate prices, build a website or submit an inquiry. Plans remain in the current tab until you download them.

Form planning

A form plan describes fields, conditions, destination mapping, delivery decisions and visitor-recorded test results. Preview success and failure are local simulations, and test answers are excluded from exports. The planner does not host a form, deliver messages, verify checklist results or configure storage.

Content conversion

Markdown and HTML conversion retains supported content elements, strips active content and reports simplification. Layout and unsupported constructs may change. Preview links are inactive and image URLs are not loaded.

HTML accessibility findings

Static markup checks identify common label, image-alternative, link, button and ID issues with source locations. Name and visibility checks are approximations. CSS, scripts, live interaction and full WCAG conformance require separate evaluation.

JSON syntax and formatting

JSON checks follow the RFC 8259 grammar. Formatting and minification change only whitespace between tokens, preserving number spellings, string escapes and member order. Duplicate keys and unpaired Unicode escapes receive compatibility warnings. This does not validate a JSON Schema or application rules.

Delimited data conversion

CSV cleaning applies only selected transformations and reports changed cells and removed rows. Column selection, header names and order are applied afterward; excluding columns never removes more rows. Values remain strings. Quoted fields preserve separators and line breaks. Formula prefixes and optional UTF-8 BOM bytes are disclosed separately for delimited exports.

QR encoding

QR codes encode the supplied URL, text, email, phone or Wi-Fi details with a locally bundled encoder. PNG and SVG preserve the same pattern and four-module white border. Email and phone codes prepare an action on a compatible device; they do not send messages or place calls here. Wi-Fi codes contain readable network credentials. Destination availability and device behavior need separate checks; static codes do not provide scan tracking.

Image compression

Image exports use the browser's encoder and report actual bytes. The result preview is decoded from the exported file. A target-size search tries a bounded set of JPEG/WebP quality settings at the chosen dimensions and reports when none reaches the target. It does not guarantee the smallest possible file or identical output across browsers.

Exact calculation

A deterministic result from stated inputs and a published formula or count, such as bytes, percentages, character counts, or WCAG contrast ratio.

Rule-based check

A repeatable parser, validator or generator works with supplied text, markup, URLs or rules. Campaign-link generation encodes the values you provide; it does not verify destination analytics. Structured-data generation checks its supported templates and field formats, not search eligibility or a live page. Sitemap checks read the supplied file and supported core fields; extensions, live pages and indexing are not verified. Redirect-map checks follow supplied rules with documented URL matching; they do not test live responses. These checks do not infer how every browser or search system will behave.

Editorial suggestion

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. Social artwork is rendered locally at 1200 × 630 pixels using measured text and static raster images. PNG/JPEG exports do not publish the image, verify its public URL or guarantee a platform's final crop.

Planning or readiness check

A checklist confirms that documented questions were considered. Completion does not forecast indexing, traffic, citations, accessibility, or business results.

Live website checks — unavailable

Plainview Tools does not currently scan live websites. Internal-link suggestions use the page inventory and text you provide, so existing links need a separate check.

Sources

Primary documentation comes first.

Guidance links to the relevant platform documentation or technical standard. Review dates show when source-based advice was last checked, so you can judge whether a rule may have changed.

Your data

Most tools run in your browser.

Most text checks, calculations, previews, and image tools process your work in the browser tab. The font previewer's optional Google Fonts requests are explained below and beside the font controls.

Browser processing

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.

Internal-link suggestions

Compare the pages you provide.

Pasted page inventories and target copy are compared in your browser. Live scanning is unavailable. These results do not verify existing links or other content on the live site.

Open Internal Link Suggestion

Optional Google Fonts

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.

Open Font Pairing Previewer
Your tool inputs stay out of analytics.

Optional 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

Check when the guidance was reviewed.

Review dates show when guidance was last checked against its sources. Platform behavior can change after that date; follow the linked documentation when a decision depends on the latest rule.

  1. Source documents

    Links identify the specification or platform guidance behind a rule.

  2. Methods and limits

    Inputs, assumptions, formulas, and exclusions explain how to read the result.

  3. Practical checks

    Calculations, explanations, and representative edge cases are checked as tools are maintained.

  4. Review dates

    The displayed date records a review of the guidance; it is not a promise of future platform behavior.