A measure you can understand
Action Presence Score.
A transparent method.
Our Website Screening score summarizes the supported public-HTML checks we can run. Save your initial screening, then manually recheck after approved changes to see what the same checks observe.
One clear formula.
Each checked page has nine core check types. Every available page/check observation has equal weight. A pass contributes one; an item marked review contributes zero. Unavailable observations are excluded from the calculation and displayed separately.
A score requires at least six of the nine core checks to be available on every checked page. A planned linked page that cannot be checked makes the screening coverage insufficient. If coverage is insufficient, the result is not scored, rather than zero. Coverage, check date and page count remain visible. Other unavailable checks, such as structured-data validation, are outside the score.
Color bands with a defined scope.
The instrument shows our own website-screening bands: red 0–49: Review signals; amber 50–79: Build consistency; green 80–100: Strong signals. They describe the proportion of supported checks that passed, not Google rankings or overall business health. These display thresholds are Action Enterprises conventions, not industry benchmarks. Unscored results stay neutral and have no score needle.
An optional next-service match uses the actual screening, coverage, your selected priority and any verified comparison. It is an invitation to agree useful work, not a finding, automatic purchase or promise of score or revenue improvement. Profile care has a separate purpose and does not raise the website score by itself.
The nine core check types.
- HTTPS on the fetched URLWhether the observed final public page URL uses HTTPS. This is not a security audit.
- Fetched page responseWhether the supplied response status is successful. Error or challenge pages are not diagnosed as the business page.
- Page titleWhether a non-empty title was established in the inspected HTML.
- Description metadataWhether a non-empty description meta field was observed. Search services may rewrite or ignore it.
- Mobile viewport declarationWhether width=device-width was observed. The screening does not render or prove a usable phone layout.
- Explicit indexing exclusion directiveWhether an explicit noindex/none directive requires review. No observed directive does not prove indexing or ranking.
- Primary heading clarityWhether the HTML main-heading structure warrants review. Multiple H1 elements alone are not proof of a penalty or a poor user experience.
- Detected contact or inquiry pathWhether a supported phone, email, contact link or possible inquiry-form pattern was detected. Destinations and form submissions are not tested.
- Image text-alternative observationsWhether a supported informative-image candidate requires review. Ambiguous image purpose is unavailable; decorative images may legitimately use empty alt text. This is not a full accessibility audit.
Some checks cannot be interpreted reliably in blocked pages, application shells or incomplete material. We mark them unavailable instead of inventing a failure. A review flag calls for contextual confirmation; it does not automatically justify an edit.
Compare the same things.
A point change is shown only when the server can verify both private saved snapshots have the same exact website URL, scoring version, analyzer version, page set and available check set, with the baseline strictly earlier than the current screening. Different page coverage, unavailable checks or method versions produce an explanation and no improvement figure.
The comparison also counts checks that moved from review to pass, pass to review, or stayed unchanged. A zero-point change is shown as Score unchanged. The first screening establishes a baseline; it is not reported as improvement. You can explicitly select a different saved screening using the baseline selector.
A higher score confirms a change in the supported observations. It does not prove who caused the change, that the website is fully optimized, or that rankings, inquiries or sales improved. Actual customer and business results need separate measurement.
Website signals, with clear limits.
This screening reads up to three supported public pages. It does not cover the entire website, JavaScript-rendered behavior, every device, real form or booking success, performance, security, full accessibility, Google rankings, leads or sales. A high score means these supported checks passed; other issues may still exist. The score does not determine whether a paid report offers enough value.
Google Business Profile is not scored. Finding a website-linked Google Maps reference does not verify the listing, location, ownership, eligibility, profile quality or rankings. Any profile review and agreed optimization are separate work. We are an independent service and are not Google.
Your baseline, retained separately.
Score-only snapshots have a 90-day server and browser expiry. They contain the public website URL, page/check identifiers and statuses, counts, dates and scoring versions. They exclude captured page evidence, detailed findings and recommendations. Your browser also saves private comparison access; do not share browser-storage contents.
This browser retains up to 12 snapshots, preserving retained baselines before older follow-ups. When space is required, an old website group may be removed together. Expired or removed baselines are not silently replaced. Without valid saved access, you may need to establish a new baseline; a downloaded history file omits private tokens and cannot restore server access.
Original free captured-report access remains 7 days. An issued checkout attempt or verified purchase can retain that original report for up to 90 days under its own access rules. Score history never extends or unlocks detailed-report access.
The separate history control removes this website's saved score history from this browser. The report-access control also removes its corresponding score snapshot locally. These controls do not delete server records, cancel purchases or change marketing preferences. Server snapshots expire under their retention limits. Manual rechecks use the ordinary screening allowance. You may separately request the free seven-day daily monitoring beta in the dashboard. Background checks require confirmed hosting activation and explicit opt-in; the initial trial begins with its first actual hosted check attempt. No website changes, purchases, marketing signup or automatic renewal are created. Monitoring jobs and their public website references are retained for up to 90 days; each score snapshot has its own 90-day expiry.