Website review
Improving an inquiry form
Original work sample · Market Wrangle’s own website · October 14, 2026
A useful website review should connect an observed problem to a specific change and a way to check it. This example examines the route from Market Wrangle’s service pages to its inquiry form. It uses my own website, so it does not depend on client naming permission or claims about work completed for an agency.
Inside this sample
01 / The question
The question
Could someone requesting a website report provide the information needed for a review? Could someone asking about a new project or agency support reach the same form without being treated as a report request?
02 / Visitor intent
Finding 1: the buttons needed to carry the visitor’s intent
Observed
The project and agency buttons previously pointed to a section below the form. That meant visitors could arrive past the place where they needed to enter their details. The report links also did not explicitly select the report option.
Changed
The revised links land at the form and preselect the matching request: a free visibility report, help with a project, or agency support. Visitors can change that selection. Opening Contact directly leaves the choice open.
03 / Useful requests
Finding 2: a report needs a website to review
Observed
The original form allowed a report request without a website URL. That could create a follow-up exchange before the review could begin. Making the website mandatory for every inquiry would also create a problem for someone planning a new site.
Changed
The form now asks for the request type first. A website is required for a free visibility report and optional for other inquiries. “Service area or audience” gives local businesses and organizations serving a broader audience a relevant way to describe who they want to reach.
04 / Functional checks
What was checked
- Report links opened the form with the report option selected and a required website field.
- The Services project button and For Agencies button selected their matching inquiry types.
- A blank report submission displayed a website validation error. A blank project submission did not require a website.
- Opening Contact directly displayed “Choose a request type.” Selecting a report displayed the required website field.
- These checks did not create a new inquiry or send a notification email.
05 / What it demonstrates
What this demonstrates
The changes make the form ask for information appropriate to the request. They demonstrate review, copy, form configuration, and functional testing. They do not establish an increase in inquiries or sales. That would require observations from real visitors over time.
06 / Sources & scope
Sources and scope
Source material: Market Wrangle’s own Services, For Agencies, and Contact pages, plus its WordPress form configuration. Initial review: October 13, 2026. Changes and functional checks: October 14, 2026. This is a focused inquiry-flow example, not a complete technical SEO audit or a client performance case study.