Start with a real observation
Give the client a clear point to react to, not a generic pitch.
Before a pitch, manual website checks can consume time you meant to spend understanding the client. PageAnalyser is being built to turn a prospect’s public page into a focused starting point for discovery. This version is under construction; test requests help validate the workflow.
Start the conversation with something specific. Find out whether it connects to the client’s goals, then spend proposal time on work they actually value.
Give the client a clear point to react to, not a generic pitch.
Use focused questions to understand goals, constraints, and the next action they want from visitors.
Turn what the client confirms into work with a clear purpose and boundary.
A useful first question starts with a detail the client can see. Their answer tells you whether it belongs in the offer.
Evidence: no page description was found. If search discovery matters, agree the offer’s key distinction before proposing a snippet.
Evidence: no viewport setting was observed. Confirm the real mobile experience before quoting a layout change.
Evidence: none of the selected English action phrases matched the visible links and buttons. Check labels and destinations manually before recommending a change.
Examples show how a page detail can guide discovery. Verify the evidence and the client’s goal before you advise or estimate.
A quick first look can help you decide whether a lead merits deeper research. Reserve detailed analysis for qualified work, then price the scope against what the client confirms.
Use a first pass to decide if this lead deserves a full analysis.
Take a useful question into discovery, then agree the depth of analysis as paid work.
Estimate once the goals, platform, and any shared-template impact are confirmed.
Take a few verified observations and questions into discovery. Listen for what the client values, then shape a recommendation they can see the reason for.
Prepare for a real prospectMake the proposal about the client’s next step, not the hours you spent researching.
Learn what PageAnalyser is being built to do, what a test request validates, and what is not available yet.
Submit a test requestIt is being built for agency owners, freelancers, and consultants who spend unpaid time researching a prospect before they know what to propose. The planned review is meant to help you arrive with specific points to confirm and make better use of discovery calls. Live reporting is not available in this prelaunch version.
The request is stored in a protected queue for workflow validation. Queue acceptance does not confirm that analysis completed or that an email was delivered. This build is not offering live reports yet.
Live report delivery is not available yet, and this page does not give a launch date. Test requests may be used to validate the page check, Lighthouse assessment, interpretation, PDF creation, and email flow. A queue confirmation only means the request was received; it does not confirm a report or email.
No. The planned review is intended to give you evidence to discuss in discovery. Your conversation with the client determines which observations matter, what belongs in scope, and what you should charge.
The planned review is designed for a public page and does not require client logins, analytics, or search-account access.
The planned review covers one submitted public page using its initial response, a browser-rendered page, and one mobile Lighthouse lab run with simulated throttling. It is not designed to crawl a whole site, use Search Console or private analytics, or measure real-user Core Web Vitals, rankings, traffic, or conversions. Live reporting is not available in this prelaunch build.
No. Marketing emails are optional and do not affect a test request. PageAnalyser is not currently sending marketing emails, and this version does not save your checkbox choice.
Submit a test request to exercise the queue and delivery workflow. Queue acceptance is not a promise that a report email will arrive.
Submit a test request No marketing opt-in required