See which findings changed along with the score. Then check the inquiry process and inquiry data separately. The score summarizes the results of technical checks, but it does not calculate revenue or show whether a manager responded to a customer.
For a fix, you need a direct result: the intended navigation, title, or form submission. To assess inquiries, you need company data for a comparable period. These questions can have different answers.
See what contributed to the change
When comparing two audits, look not only at the overall score but also at the findings. A change in one category can affect the score while an important individual issue remains. Sometimes a specific URL is fixed, but other checks reveal new issues.
Check the date and scope. If one run examined one sample of pages and the other examined a different sample, the totals need context. The daily automated audit of a connected site has a limit of up to 100 URLs. A large catalog cannot be considered fully audited based on a single report like this.
For example, product titles changed, but the form stayed the same. Record the URLs with corrected titles. The list of technical issues is covered in the SEO audit guide. The score change alone does not explain the number of inquiries.
If the score went up but the form still does not deliver inquiries
Suppose a developer removed duplicate Title tags from product pages, and the technical score went up. But the manager cannot find the test order. Title is the page name in a meta tag, usually visible in the browser tab; changing it does not fix order delivery.
Record the technical fix using the new values. Then create a separate task for the form: the URL, steps, test time, response screen, and where the submission is missing. Run an agreed test with the recipient, without treating a success message as the final result.
To assess any change in actual inquiries, get the data from the company’s system and clarify the period, traffic source, and any advertising changes. If this data is unavailable, write “impact on inquiries not assessed.” Do not enter zero in place of missing information.
If an issue was fixed but the score stayed the same
Suppose a service link in the menu now works. At the same time, the new audit found other issues, so the overall score did not go up. Accept the navigation fix: the intended page opens from the agreed URLs.
| Observation | Result already known | What to check separately |
|---|---|---|
| Link fixed, score unchanged | Navigation works | Other report findings |
| Score higher, same number of inquiries | The specified checks improved | Traffic, form, offer |
| Site responds, order does not go through | URL returned a response | Full order flow |
For a specific fix, save the publication date and the URLs checked. The detailed process is in the guide to accepting work.
Frame the owner’s next question
Get the latest report from the monitoring dashboard and separate confirmed work from what still needs to be learned. For example: “Product titles have been fixed; the impact on inquiries is not yet known; today we’re testing the form with the manager.”
If the form works but inquiries have decreased, compare the company’s own data: visits to relevant pages, demand, advertising, and inquiry handling. Choose one question for which data is available. Do not assign the developer the task “raise the score so sales go up” without a direct change to the website.
In the next report, label the score with its date and the pages checked, and label the number of inquiries with its source and period. This will help everyone involved understand which result changed and what to check next.