Business Website Health Checker
Pricing
from $4.90 / 1,000 page auditeds
Business Website Health Checker
Produce a quick health report for a business website: technical basics, metadata, links, schema, and performance hints.
Pricing
from $4.90 / 1,000 page auditeds
Rating
0.0
(0)
Developer
junipr
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Audit a business page for practical technical, metadata, schema, linking, mobile, and conversion-path signals.
Business Website Health Checker is designed for small-business owners, agencies, SEO teams, developers, and operators checking a bounded page set. It processes only the bounded inputs you provide, produces deterministic dataset rows, and writes optional JSON and Markdown reports. Empty, blocked, or malformed sources are represented as diagnostics rather than successful invented data.
Common Uses
- Find indexability, title, description, canonical, and H1 problems.
- Check whether LocalBusiness or Organization JSON-LD is present.
- Verify that visitors can find a phone, email, contact, quote, or booking path.
- Create a concise technical report before a page launch or campaign.
How The Analysis Works
- Each page receives ten deterministic checks: HTTPS, indexability, title, description, canonical, H1, business schema, contact path, internal links, and viewport.
- Pass rows represent extracted controls. Warning and failure rows represent findings with evidence, impact, and a remediation.
- Title and description checks include practical length bands. Indexability checks inspect the robots meta tag.
- Network retrieval blocks redirects, credentials, private addresses, oversized bodies, and long-running requests.
The actor processes source groups in order. It stops before another paid row when the run's event charge limit is reached. Rows already charged and written remain available, and the summary marks the run as truncated. Source-access diagnostics do not pretend that an audit or analysis succeeded.
Input
html or text: inline page source for deterministic analysis.urls or sourceUrl: public HTTP(S) pages fetched only when fetchUrls is true.maxItems caps checks per page; use 10 for the complete check set.maxTargets caps pages and maxTextBytes caps each fetched response.fetchUrlsdefaults tofalse. Set it totrueonly for public HTTP(S) sources.fetchTimeoutMsis bounded between 1,000 and 30,000 milliseconds.maxTextByteslimits each fetched response to at most 1,000,000 bytes.includeReportcontrols the charged JSON and Markdown report artifacts.dryRunvalidates the input shape without paid dataset output.
Direct top-level source fields are useful for one source group. Use targets for multiple independent groups. Public URL retrieval rejects embedded credentials, redirects, localhost, private and reserved network ranges, DNS answers that resolve privately, oversized responses, and requests that exceed the timeout.
Example Input
Dataset Output
- checkType identifies the technical or conversion control.
- status is pass, warn, or fail; severity expresses operational priority.
- evidence records the extracted value or the missing-control observation.
- businessImpact and recommendation explain why the row matters and what to change.
Every row also includes a stable rowId, sourceId, optional sourceUrl, sourceType, status, severity, score, summary, recommendation, timestamp, pricing tier, and the event name associated with that row. The dataset schema is strict, so examples and runtime rows use the same field set.
Example Output
Report Artifacts
When includeReport is enabled and report charges succeed, the default key-value store receives:
BUSINESS_WEBSITE_HEALTH_CHECKER_RESULTS.jsonwith the charged dataset rows.BUSINESS_WEBSITE_HEALTH_CHECKER_SUMMARY.jsonwith counts, truncation state, and the run recommendation.BUSINESS_WEBSITE_HEALTH_CHECKER_REPORT.mdwith a buyer-readable report.
The dataset remains the row-level source of truth. The summary and Markdown report are derived from rows that were actually emitted; they do not include rows stopped by a charge limit.
Pay Per Event
This actor uses pay-per-event pricing. The configured event prices include platform usage, and the default maximum charge is $10.00. The actor charges before paid output and rejects partial charges.
actor-start: $0.00500 per event. Charged before paid dataset output or the corresponding paid unit is emitted.page-audited: $0.00490 per event. Charged before paid dataset output or the corresponding paid unit is emitted.record-extracted: $0.00372 per event. Charged before paid dataset output or the corresponding paid unit is emitted.finding-emitted: $0.00372 per event. Charged before paid dataset output or the corresponding paid unit is emitted.audit-report-generated: $0.05000 per event. Charged before writing the buyer-ready report artifacts to key-value storage.
Discounted Store tiers are represented in the pricing metadata. Review the run's cost estimate and caps before increasing source counts. URL retrieval, proxy use, or external services are not silently enabled by the actor.
Public Tasks
- Audit public URLs for Business Website Health Checker issues: Audit one capped public page for technical, metadata, schema, link, and contact-path issues.
- Find Business Website Health Checker problems across a website: Check a small URL set for page-health failures and evidence-backed warnings.
- Generate a technical Business Website Health Checker report: Generate a concise page-health report from supplied HTML without a network request.
- Validate business schema and contact conversion paths: Focus on LocalBusiness JSON-LD and visible call, email, quote, or booking paths.
- Check indexability, canonical, title, and H1 signals: Review core search visibility controls on a bounded inline page sample.
Each task uses a small explicit input and sets a maximum item count. URL-based tasks enable fetching only where fetching is necessary to demonstrate the actor's purpose; inline tasks remain deterministic and network-free.
Reading Results
Start with blocked or high-severity rows, then review attention or warning rows. Confirm the evidence and recommendation against your operating policy before making bulk changes. A pass means the supplied source satisfied the configured check; it is not a guarantee about data or behavior outside the source and rules evaluated in that run.
For repeated workflows, keep source IDs stable. Stable IDs make it easier to compare exports, trace a report row to the original input, and identify whether a change came from source data or configuration. Keep caps low while testing a new data shape, then increase them only after confirming row counts and expected event costs.
Data Handling And Safety
Use public or authorized source material. Do not provide credentials in URLs. The actor does not attempt to bypass authentication, anti-bot controls, access restrictions, or private networks. Fetched bodies are held only for the run's bounded analysis. Dataset and report outputs may contain excerpts or field values from the supplied source, so avoid submitting secrets or personal data that should not appear in Apify storage.
Limitations
- The actor does not run Lighthouse, execute page JavaScript, or measure Core Web Vitals.
- Regex-based HTML inspection is designed for common page markup and does not replace a browser rendering audit.
- Schema presence does not guarantee that every property is valid for a rich result.
- A page passing these checks can still have content, accessibility, performance, or conversion problems outside this scope.
FAQ
Does the actor invent missing values?
No. Missing values and unavailable sources become explicit gaps, mismatches, failures, or diagnostics.
Can I run it without network access?
Yes. Supply inline records, CSV, text, or HTML and leave fetchUrls disabled.
What happens at the charge limit?
The actor stops before the next paid output, preserves rows already written, and marks the summary as truncated. Optional report artifacts are written only when their report events are fully charged.
Should I treat every finding as an automatic change?
No. Findings are deterministic QA or analysis results based on supplied evidence. Review business context, source quality, and intentional exceptions before acting.
