It's free, continue with GooglePostCliq is a free website audit that ends in three quick wins: the findings most likely to stop visitors enquiring, each with its evidence, its action and a way to check the fix worked. This page explains how they are chosen and what happens after you act.
Audit your websiteShort attention spans are the design assumption. Findings are ranked by how directly they affect the enquiry journey, how many pages they touch and how confident the evidence is, and the top three become quick wins. They read as one-line headlines under a single heading: three things you can do. The other findings stay in the report, grouped by category, one click deeper.
Three things you can do
Each quick win opens to the affected page, the captured evidence and the date. A form with eleven fields, a hero image weighing three megabytes, a call to action that says "Submit". You can see it the way the crawler saw it, and decide whether the observation still holds before anyone spends an hour on it.
Every finding carries all four. No evidence, no finding.
A plan is not a verified fix, so the report keeps the distinction: the next weekly audit runs the same check on the same page. If it passes, the history shows it. If it does not, the finding comes back with the new evidence rather than quietly disappearing. You can mark a quick win as planned, changed or dismissed inside the report, and only an audit marks it verified.
| Edition | Health | Open priorities | Change |
|---|---|---|---|
| 5 Sep | 61/100 | 3 | — |
| 12 Sep | 64/100 | 2 | +3 |
| 19 Sep | 68/100 | 1 | +4 |
Mark a fix, recheck the same scope, and the history shows whether it held.
Connect Google Analytics or Search Console and the enquiry rate for the page you changed sits beside the finding. A recheck tells you the form is shorter; the traffic context tells you whether more visitors enquired. Both are signals to read together, never proof of a single cause.
Consulting attracts attention. Its enquiry rate needs a closer look.
| Landing page | Sessions | Enquiries | Rate |
|---|---|---|---|
| /services | 4,200 | 84 | 2.00% |
| /consulting | 2,800 | 28 | 1.00% |
| /contact | 1,650 | 66 | 4.00% |
Open the source, confirm the date range and segment, then use the signal to choose a page-level check. This example is illustrative and is not an attribution claim.
What it means, how it works, where the evidence comes from and what assumptions apply. Keep the overview calm; keep the working available.
See the methodologyWebsite fixes ranked by effort and impact, from the quick to the structural.
How to increase your conversion rateThe last step is where most enquiries are lost. What to cut, keep and test.
Read the contact form guideHand a quick win to a developer with everything they need to ship it once.
How to brief a website fixType your address on the homepage. PostCliq reads your public pages the way a careful visitor would. No login, no plugin, no card.
Create a free account while the checks run. Your report shows what was found, the evidence for it and three quick wins to make first.
Make the change, run the next weekly audit and see whether it held. Connect Analytics, Search Console or Clarity when you want traffic context.
The ones close to the enquiry that touch many pages: a form asking for more than it needs, a call to action that says "Submit", a heavy hero image slowing the mobile page, a contact path buried in the footer, or a missing page heading. They rank high because they sit on the path to an enquiry, reach many pages and leave clear evidence. Each is a specific change, not a rebuild.
They are sized so a team can ship them between one weekly audit and the next. The report says what to change and where, so the time goes on the change rather than on working out the problem. The next weekly audit then checks whether it held.
Code does, from the evidence. Findings are ranked by their effect on the enquiry journey, how many pages they touch and how confident the evidence is. AI helps explain each one in plain language; it does not decide the order.
Every finding is in the report, grouped by category, one click below the quick wins. Three is the number at the top because three is what a team actually does before the next audit.
By the next audit, not by anyone’s say-so. The next standard audit runs the same check on the same page under the same conditions. If it passes, the finding is shown as verified and the history records the change. If it does not, the finding comes back with the new evidence. Telling PostCliq you made the change is a note for your team; it never marks a finding fixed.
Yes. Dismiss it inside the report and give the reason. It stays in the list with that reason, so the decision is visible to the next person who opens the report, and the evidence beside it shows why you made the call.
Rechecks run on the next standard audit, and each site gets one every rolling seven days because every audit costs real money to run. A qualifying referral earns an extra run if you need one sooner. Weekly is also a sensible rhythm: most fixes take a few days to ship and a few more to show in traffic.
No. PostCliq reads your public pages the way a visitor would and writes nothing to your site. It never logs in, never submits a form, never installs a plugin and never edits a campaign. The fixes are yours or your developer’s to make; the next weekly audit checks whether they held.
Enter your address. See what stops visitors becoming enquiries.
Evidence first, three fixes, no card.
Free. No credit card.