Stride

Customer questions

Check whether your offer pages answer the questions someone needs answered before choosing you.

Last updated 2026-11-12

On this page

Customer questions reviews the practical buying questions your public pages answer, what remains unclear, and which existing page could explain it better.

Overview

Open Insights → Customer questions when the pilot is available for your selected site. It is separate from AI Readiness: readiness checks technical access and readability; Customer questions reviews the information a prospective buyer needs. Neither the assessment nor its findings change your readiness score or Visibility Index.

An offer is a service, product, product family or software plan. Stride checks each offer against relevant questions, rather than assuming that information found somewhere on your site answers the question for every offer.

For example, a local installer might need to explain service areas and quote inclusions. A shop might need fit, delivery and return information. A software product might need workflow compatibility, switching requirements and limits.

This is a review of published information, not evidence that a question has caused lost sales or that answering it will increase conversions.

How to use it

  1. Select your site and open Insights → Customer questions.
  2. Setup is one screen. Start with the product or service: review the suggested name and fill in any missing details (what customers buy, who it is for and where they are). Suggestions are not confirmed facts; correct anything that is off.
  3. Under Pages to check, choose the main page by its title, or enter a URL. Your homepage is fine when that is where you explain what you sell. Suggested supporting pages are already ticked; use Add more pages for other pricing, delivery, returns or FAQ pages. Answers there count too.
  4. Under Customer questions, remove a suggestion that does not apply or add a specific question your customers ask. Use Edit to change the wording, or to keep a question on record as left out with a reason.
  5. Choose Confirm setup. This saves your choices without checking pages or generating content.
  6. Choose Check these pages when you are ready. You can leave the page and return to its saved status. Use Edit setup to change future checks.
  7. Read the opening line, then the list. Every question you chose appears once, with the ones that need attention first and a suggested fix beside each. Open a question to see what your pages say, what is missing and the exact passages. Conflicts show both statements side by side.
  8. If the fixes are useful, choose Add fixes to Actions under that product (the button shows how many) to open its saved Action. Answered questions stay in the same list so you can check the answer and its source.

Related improvements for one offer page are grouped rather than creating work for every checklist field. Opening or adding an Action does not write a draft, select a generation destination or publish a change. Those are separate choices in the existing Actions workflow.

What the results mean

Result Meaning
Answered Relevant reviewed passages provide a usable answer for this offer, including material restrictions.
Partly answered The reviewed pages answer part of the question, but leave a specific relevant element unclear.
Conflicting answers Comparable passages disagree about the same offer and buying context. Both sources are available for review.
Not answered The applicable question was not answered on the pages you chose and Stride could read. This is not a claim about your entire website.
Couldn’t check Missing context, unreadable sources or an assessment problem prevented a defensible result. This is not a content failure or a pass.

A question you excluded is not counted as missing. An answer can be negative: “not compatible with Android” or “custom orders cannot be returned” still answers the question when clearly published. Different variants, markets, billing periods or dated offers are not automatically conflicting.

Stride may also list separate observations under Also on these pages, such as an expired offer that is still published. They belong to the product but not to one question.

Technical details lists the pages read, unavailable sources and collection limits. An incomplete or failed run never means your site has no gaps. If an older result remains visible during a recheck or after a failure, it is labelled Previous results and keeps its original date.

Custom pricing is legitimate

You do not need to publish a fixed price just to satisfy this assessment. Useful information can include what a quote covers, common extras, cost drivers, ranges, worked examples or how the quotation process works.

“Contact us for a quote” can explain the next buying step without explaining what is included. A useful finding names that distinction and suggests a specific improvement to the existing page. Stride does not invent prices, promises or terms to complete an answer, and this assessment does not research competitors' prices.

Best practices

  • Start with the offers you most want reviewed, not every page on your site.
  • Include the supporting pages that genuinely explain each offer's terms.
  • Keep restrictions visible: an honest limitation is useful buying information.
  • Prefer improving the existing offer page over creating another blog post.
  • Check source dates and applicable terms before changing published claims.

Availability and limits

Customer questions is a selected-site pilot, not a generally available plan entitlement. If the Health item is absent, it is not enabled for that site.

The pilot scope allows up to three offers, eight questions per offer and twelve unique same-site public pages across the assessment. Shared supporting pages are read once. Narrow the scope if it exceeds the displayed limit; saving extra pages does not silently authorise a larger crawl.

The collector reads public static HTML. Pages beyond the HTML/text limits, JavaScript-only pages and sources that cannot be safely read are not treated as clean evidence. Connected product catalogs, private pages and business listings are outside this assessment.

Completed or partial manual assessments have a 24-hour recheck interval. Failed attempts have a five-minute retry delay. Refreshing AI Readiness does not start this offer-question assessment automatically.

FAQ / Troubleshooting

Why couldn’t a question be checked?

Open the question to read the reason, then open Technical details. Check the offer context and selected pages first. A blocked or unreadable page cannot establish that information is missing. Correct the scope or source issue, then recheck when available.

The answer exists elsewhere. What should I do?

Add that relevant supporting page to the offer's scope and save it for the next assessment. A result applies only to its reviewed pages. Private setup notes do not prove the answer is published.

Will a finding automatically fill my Actions queue?

No. Review the suggested fixes and choose Add fixes to Actions. Confirming setup or checking pages does not generate content or publish changes.

Why do I still see an earlier finding after an incomplete recheck?

An unreadable page, changed scope or failed assessment cannot prove an earlier issue was fixed. Existing work and its source evidence remain available. Work you already started is not discarded when you run another assessment.

Why is an earlier result labelled as an older format?

Earlier pilot checks used a different, broader checklist. Their saved evidence remains available, but Stride does not pretend those checks answered the new offer-specific questions. Confirm your scope before running a new assessment.

— Free audit · no account requiredFree breakdown · no account required

See where you stand
in the answers that matter.

See your measured mention and citation outcomes, the competitors AI recommends instead, and three evidence-backed fixes — free.