Frequently Asked Questions - Websites

Improve the current site when its structure and publishing tools still support your goals and the main problems are messaging, content, calls to action, or performance. Consider a rebuild when several foundational problems overlap:

• The navigation or content structure no longer fits the business.
• The website platform or theme prevents routine marketing changes.
• The path from a visit to an inquiry or sale needs more than a few targeted fixes.
• Past fixes have made the site slow, fragile, or expensive to maintain.

Start with an assessment of those areas. Focused improvements are usually the better investment when the foundation is sound; a rebuild makes more sense when the foundation itself is holding the website back.

WordPress may be a better fit when your requirements align with its hosting model, available themes and plugins, developer ecosystem, or a specific integration your team has verified. Before deciding, compare your maintenance capacity, data ownership and hosting requirements, integration needs, editor workflow, and total cost. Confirm each needed capability in the actual host, theme, plugins, and services you plan to use. A broad claim about customization or ecommerce is not enough to make the decision.

StoryBrand is a messaging framework that positions the customer as the central character and the business as a guide. Use it to pressure-test three parts of your hero:

• Problem and outcome: Show what your visitor wants or needs to change.
• Guide: Make it clear how your business helps without making the message all about the company.
• Next step: Give the visitor a specific, appropriate action.

The result should be clear in a few seconds, even for someone who has never heard of StoryBrand.

Start by writing down what visitors must be able to do, the workflow your business needs, the data involved, and any systems the website must connect with. Then compare those requirements with the theme, reusable page sections, and platform features you already have. Use this order:

1. Use an existing solution: Choose a built-in feature or trusted app when it solves the need cleanly.
2. Adjust what you have: Change existing theme or module settings when the capability already exists.
3. Add a focused extension: Enhance the existing solution when most of what you need is already in place.
4. Build custom: Choose custom development when an essential requirement cannot be supported cleanly by the available tools.

A unique page layout does not automatically require a custom build. Custom development is justified by a real capability gap, not simply by wanting the site to look distinctive.

You do not need every detail frozen before development starts, but the decisions that shape the build should be approved. Confirm these basics first:

• The business goal, sitemap, and purpose of each page.
• The design direction and content plan.
• The platform, technical requirements, integrations, and SEO migration needs.
• Who approves the work and how changes will be handled.

Draft copy, imagery, and smaller presentation details can continue to improve during development when the schedule allows. Set deadlines for those items so unfinished content does not change the structure or delay the build.

Start by finding where the website is losing business opportunity instead of changing everything at once. Use this order:

1. Define the business goal and the conversion path visitors should follow.
2. Record a measurement baseline for traffic, engagement, leads, and conversions.
3. Fix critical technical failures that block visits, forms, tracking, or search access.
4. Review the message, priority pages, and calls-to-action for clarity.
5. Improve performance and accessibility issues that make the experience harder to use.

This sequence helps you fix the biggest leak first. For a broader diagnostic, review 10 signs your website might be underperforming.

A strong homepage hero helps the right visitor understand the business and choose a next step quickly. Check for:

• Audience and value: The message says who the business helps and why it matters.
• Specificity: The wording is concrete enough to mean something.
• Proof and visuals: Images or evidence support the message instead of competing with it.
• Action: The primary call to action fits the visitor's likely next step.
• Readability: Text, contrast, reading order, and buttons or links remain accessible.
• Mobile performance: The section stays clear and fast on a small screen.

It can, and the amount depends mostly on how much content your site needs and how much research is already complete. Planning may include researching real customer questions, writing concise answers, organizing pages around those needs, and creating useful internal links. Accurate structured data may also be added where the page and content qualify, but there is no special schema that automatically makes a page ready for answer engines. Doing this work during the build is usually more efficient than reorganizing the site after launch.

No. The 0–100 Lighthouse performance score shown in PageSpeed Insights is a controlled test result, not a ranking factor by itself. Google uses real-world Core Web Vitals among its broader page-experience signals, so data from actual visits can matter even when a single test looks good or bad. Use the score to find performance problems, then evaluate those findings alongside real-user data, content quality, and search relevance. Google's Core Web Vitals guidance explains how the real-world metrics fit into search.

No. WordPress is not bad for business websites. A well-planned and well-built WordPress site can be fast, flexible, strategic, and effective.

The problem is not the platform itself. The problem is the habit of adding features, plugins, animations, layouts, and sections because they are available rather than because they serve the visitor or the business goal.

WordPress works best when the site is guided by strategy, performance discipline, content clarity, and a real maintenance plan.