CTA candidates
Looks for links, buttons, and other visible candidates that suggest a next action. It does not judge persuasion or conversion rate.
FREE LANDING PAGE READINESS CHECK
日本語
Free · No sign-up · Automated
Check a live landing page before your next move
Enter a URL to check the public HTML for CTA candidates, pricing, FAQ structure, payment or application routes, legal links, and basic mobile settings. No email address required.
This tool does not declare a page good or bad. Use its results to decide whether to keep the page, make a focused repair, or compare a more complete template structure.
FreeNo charge for the basic check
No sign-upNo account required
Public URLsFor retrievable pages
ReferenceScore and item-level signals
01 — FREE CHECK
Start with the public URL you already have
Enter a landing-page URL that anyone can open. Use only a page you own, manage, or have authority to audit. The diagnostic engine checks basic candidates in the HTML it can retrieve.
Automated diagnostic engineLoaded from the audit service
If the diagnostic does not appear, review browser settings and use the troubleshooting steps below.
02 — AUTOMATED SCOPE
The automated scope is limited to these six checks
This is not a Core Web Vitals test, conversion-rate assessment, comprehensive security scan, accessibility certification, or legal review. The scope below is deliberately precise.
Pricing and plan cues
Looks for visible pricing, cost, or plan candidates. It does not verify amounts, contract terms, or disclosure compliance.
FAQ structure
Looks for FAQ headings, question patterns, and details elements. The accuracy and completeness of each answer still require review.
Payment or application route presence
Looks for links or form elements leading toward purchase, booking, application, or enquiry. It never submits a form or completes a purchase.
Legal-link candidates
Looks for links such as terms, privacy, and disclaimers. Detection is not a legal-compliance assessment.
Mobile settings
Looks for basic signals available in fetched HTML, including a viewport setting. It does not emulate every device or certify usability.
03 — READ THE RESULT
Treat the score and item-level signals as reference
The diagnostic presents an overall score, A-D grade, and item-level signals. They summarize automated detection in public HTML; they are not a promise of outcomes, compliance, or readiness.
A summary of automated detection across six basic areas. It does not guarantee sales, conversion rate, completeness, compliance, or launch readiness.
Reference signals derived from candidate elements in retrieved HTML. Verify wording, placement, destinations, and actual operation on the public page.
A missing candidate does not prove absence. JavaScript, third-party widgets, login, access controls, or retrieval errors can hide content from automation.
Do not make the launch decision from the diagnostic alone. Check desktop and mobile display and follow the authorised application path directly.
04 — NEXT BEST ACTION
Choose only the next step your result supports
Not every landing page needs a rebuild. Keeping a page that already covers the basics can be the right decision.
Keep the current page
If the main candidates are present, do not rebuild solely because you ran this check. Continue measuring genuine enquiries and user behaviour.
Compare before choosing WebP
LP Audit does not measure image weight or speed. Check file size separately, keep the original, and compare WebP size and visible quality before replacing anything.
Open the free WebP converterMake a focused repair
Add the missing CTA, FAQ, legal link, or mobile setting without discarding a design that otherwise works, then rerun the check after publishing.
Review the six-check scopeStart from a template
When important sections or the page order need a broader reset, compare HTML templates that already include a deliberate landing-page structure.
Browse 400 templates
05 — BEFORE & AFTER
Use the same checklist before choosing and after publishing
LP Audit is repeatable launch-readiness QA, not a one-time verdict. Use the six items as a manual checklist while unpublished; automation needs a non-confidential public review URL or the live URL immediately after launch.
Check the current public page
Use a URL that an ordinary visitor can open and review the retrievable basics.
Choose keep, repair, or rebuild
Combine the automated results with the page goal, maintenance effort, and real-world response.
Verify your edits directly
Open CTA destinations and check pricing conditions, FAQ, legal information, and mobile layout yourself.
Publish, then rerun the check
Use the final public URL so the diagnostic reviews the HTML actually being served.
Repeat after material changes
Reuse it when a campaign, price, form, integration, or template changes.
06 — LIMITS & PRIVACY
Use a public page and understand what automation cannot see
Easier to retrieve
- Publicly available over HTTPS
- Opens without login
- Main content is not hidden behind access or consent gates
- Important elements exist in delivered HTML
Harder to determine
- Admin, member, or internal pages
- IP rules, Basic Auth, or bot protection
- Content appears only after JavaScript runs
- Important routes live inside third-party widgets
07 — TROUBLESHOOTING
If the page will not load or cannot be determined
Check the URL
Confirm it starts with https:// and contains no accidental spaces or temporary sharing token.
Test public access
Open the same URL while signed out or in a private browser window.
Review access controls
Check whether a WAF, bot rule, region rule, Basic Auth, or consent gate blocks retrieval.
Wait and retry
After a new release, DNS and CDN changes or a temporary network error may need time to settle.
Finish with direct testing
For items that remain indeterminate, inspect desktop and mobile layouts and follow the permitted enquiry path yourself.
FAQ
Frequently asked questions
What does the free landing page check cover?
It checks retrievable public HTML for CTA candidates, pricing or plan cues, FAQ structure, payment or application route presence, legal-link candidates, and basic mobile settings such as viewport. It does not measure speed, conversion rate, legal compliance, or comprehensive security.
If the check finds no candidate, does that prove the element is missing?
No. It means the automated check did not find a candidate in the HTML it retrieved. Content rendered later by JavaScript, third-party widgets, or text embedded in images may be missed.
Will it submit my form or complete a payment?
No. It looks for candidate links and form elements but never submits, books, buys, or signs in. Complete an authorised end-to-end test before launch.
Can I check a local file, private draft, or authenticated staging page?
No. Automation requires a publicly reachable URL that opens without login. For pre-publish QA, use a non-confidential public review URL or run the check immediately after launch. Never enter an admin URL, private preview, personal information, secret, or access token.
Do I have to buy a landing page template after the check?
No. Keep the current page when it covers the basics, make a focused repair when gaps are limited, and compare the template list only when a broader structure would help.
Can I use the check after editing a template?
Yes. Publish the edited page, then check its final public URL for the same basic candidates. Pair the result with direct desktop and mobile testing.
Will converting every image to WebP always make the page faster?
No. The result depends on the original format, quality setting, rendered dimensions, caching, and delivery. Keep the original and compare file size and visible quality first.
START WITH EVIDENCE
Run the free check first. Compare templates only when structure is the issue.
Keep, repair, or rebuild with a clearer view of what the public HTML contains—and rerun the same check after launch.