Guides for Business Owners
Use these short guides to ask better questions about your website, marketing, and the tools behind them.
Should you repair or rebuild your website?
Start with a task that is not working. If a specific page takes too long to load or inquiries disappear before reaching an inbox, look for a reproducible cause. A focused repair can be appropriate when customers can otherwise use the site and the business can still maintain it.
Consider a redesign when branding or navigation no longer matches the business, or when visitors repeatedly have trouble finding the right content. Consider a rebuild when the platform or structure cannot support important requirements. List the pages and functions you want to keep regardless of which route you choose.
Explore website repair and speed optimizationHow do you read a website speed report?
Start with the exact page and test conditions. Lab data comes from a controlled test. Field data, when available, describes real visits. Do not assume a score from one page tells you how the whole site performs on every connection or device.
Check what happened during loading, whether content shifted, and whether interactions responded promptly. Use the findings to choose a change, then test the same page or action again.
Run the free MJM website diagnosticAre search rankings, maps, and AI mentions the same?
No. A search ranking is where a result appears for a search under particular conditions. A map result is tied to local information. An AI mention is a statement in a generated answer, which may or may not link to a source you own.
Begin with accurate public information and track each outcome separately. Connect the observations to the business question you were trying to answer.
Try the AI Visibility CheckWhat is a good first task to automate?
Choose a recurring job with a clear starting point and a small number of rules. For instance, you might route a new request to the right teammate and flag requests that do not match a rule.
Write down what success looks like, where the information comes from, and who will catch errors. Leave consequential decisions with the person responsible until the process is understood and tested.
Explore business workflow automationBefore replacing a site, write down what is actually broken
Make a short list of customer actions, then try the most important ones yourself. Use a phone and start from a real entrance such as a map listing or a deep service link. Note the first point where you cannot understand the offer, find the right information, or complete the task. A form failure, a confusing menu, and a platform that cannot handle orders are three different kinds of problem. Treating them separately will make a repair or redesign easier to scope.
A short decision guide for your next project
If you can describe the problem and the evidence, you do not need to know which technical service to buy first.
- Is a task broken?
Reproduce it and request a scoped repair or assessment. Record the URL, what you tried, and what happened.
- Is important information hard to find?
Review the content, layout, and site structure. Decide whether one page, a service category, or an overall redesign is the right scale.
- Is the team doing avoidable work?
Map the responsibility and handoffs first. Consider rules or an integration only if they make that work more manageable.
Before buying ads, walk the customer route
Try the page that a prospective customer would reach. Read the offer, find any conditions, and see if it is clear what happens after a booking or inquiry. Then look at what the business receives and who responds. If no one can identify whether a request fits the offer, more traffic alone will not answer that question. A campaign can be a useful test when the destination and the handoff are ready.
Before commissioning a new feature, list the systems it touches
A portal or automation may use customer records, a payment provider, email, or existing business software. Identify where information is authoritative and who needs access to it. Agree on what happens with missing or duplicate requests. Leave room for the person who owns the outcome to review unclear cases. You can often start with one handoff and limit the rest of the project to what it proves is useful.
Before calling a scan a diagnosis, review what it tested
A page-level scan can report indicators about loading, responsiveness, content movement, and basic rules. It cannot tell you whether a particular shopper received the right email or whether a specific customer completed an order. Pair the automated result with a reproduction of the task. Ask what needs a manual check and what evidence would let you mark the problem resolved. This gives a repair conversation a useful goal.
Before saying a change worked, decide what improvement means
A fixed error should be demonstrated with a repeatable test. A page that is clearer can be reviewed with the information customers actually need. A marketing change may require comparing business outcomes over time, with the same definition for each period. These are different kinds of evidence. Set the evaluation method before promising a result and keep track of what remains unmeasured.
Start with the problem in your own words
A short description, relevant page, and desired result are more useful than a platform name or a list of features you have not chosen.
