Website & digital marketing FAQs.

Pricing depends on the number and complexity of pages, content needs, custom functionality, integrations, and migration work. Share your priorities and budget range through the project form so we can define an appropriate scope before providing a proposal.

Timing depends on the scope, the availability of content, feedback, and third-party dependencies. We establish milestones after reviewing the requirements. A fixed launch date should be discussed at the beginning so the essential work can be prioritized.

Yes. We can plan a strong website foundation first and identify the next services that would support your goals. Planning future needs early helps the structure accommodate new landing pages, content, campaigns, or locations.

We need a primary contact, timely feedback, approved business information, and access to the systems included in the work. We agree on responsibilities early so decisions and content approvals have a clear owner.

The launch plan covers the agreed page content, responsive behavior, navigation, forms, and relevant integrations. Migration or redesign projects also need URL and redirect planning. The precise checklist follows the scope of your website.

Yes. Projects can be coordinated remotely using shared documents, scheduled conversations, and review milestones. Our service-area pages help you explore coverage; they do not indicate a physical office in every listed city.

Tell us which CRM, scheduling, ecommerce, email, or other systems you use. We review available integration options and access requirements before committing to a connection; not every platform supports the same capabilities.

An agency helps a business communicate its value, reach an audience, and improve the path from interest to action. Work may include strategy, branding, websites, content, campaigns, and measurement. The services in a proposal should be tied to a business need, with clear deliverables and responsibilities.

An internal team offers daily business context and direct operational involvement. An agency can add specialist skills and capacity for a defined project or ongoing program. Many businesses combine the two. Consider the work required, management capacity, budget, and the skills you need consistently.

A project has a defined set of deliverables, milestones, and completion criteria. A retainer reserves ongoing work or capacity over an agreed period. A retainer still needs clear priorities, reporting, limits, and a process for approving work outside the agreement.

Compare the actual deliverables, assumptions, content responsibilities, revision process, launch support, and ongoing costs. A lower total may exclude work included elsewhere. Ask how success will be measured and which accounts, assets, and files will be available at handoff.

Yes. A project can support an internal team with specific design, development, content, or marketing needs. We define decision makers, points of contact, approvals, and shared responsibilities so the work fits your existing process.

New requirements should be reviewed for their effect on cost, timing, and dependencies before the work begins. A change may be added to the current scope, exchanged for another priority, or scheduled as a later phase. The agreed proposal governs the process.

Different businesses need different levels of content, functionality, and support. We begin with your priorities and constraints, then define a suitable scope. Any package or recurring plan should clearly explain its limits rather than imply that every possible request is included.

We can plan editable layouts and content around your team’s needs. The handoff should distinguish routine changes you can make from custom features that require development support.

Responsive layouts are part of planning the visitor experience. We review navigation, content, images, and calls to action on smaller screens rather than treating mobile as a scaled-down desktop view.

Bring your current website, brand files, service list, and examples of sites you like. Tell us which customers you want more of and which questions your team answers repeatedly. We use that information to identify missing content and set priorities.

Not necessarily. Useful copy, strong photography, and effective pages can remain. We identify what to keep, refine, combine, or replace before design begins so the project has a clear scope.

Yes. Custom post types and structured fields can organize locations, projects, team members, or other repeatable content. We define the fields and relationships around how you need to publish and maintain that information.

Standard page content and reusable layouts can be built for visual editing. More advanced interactions may use custom code. We identify those boundaries in the project scope and explain how the finished site should be maintained.

A homepage introduces the wider business and gives several audiences a path forward. A landing page supports one offer or campaign with a narrower goal, such as requesting a consultation or learning about a specific service.

Design defines the visual experience, information hierarchy, and how people move through the website. Development makes that experience work in the browser and connects its functionality. The two should be planned together so the finished site is usable, maintainable, and appropriate for its content.

Usually, yes. A redesign does not inherently require a new domain. The launch plan needs access to the relevant domain and hosting accounts and a clear record of DNS settings. If URLs change within the site, a redirect plan should account for the old addresses.

Content migration can be included after reviewing the source platform, volume, formatting, media, and access. Some content can be transferred directly; other material needs cleanup or restructuring. We define what is being moved, what should be archived, and who approves the migrated pages.

They can if they use large media files, excessive scripts, or continuous work that competes with page interaction. Motion should support the experience and respect reduced-motion preferences. Asset sizes, rendering cost, and mobile behavior need review alongside the visual design.

Accessibility considerations include headings, keyboard navigation, form labels, readable contrast, image alternatives, and motion controls. The exact testing scope should be agreed in the proposal. A design review alone is not a certification that a website meets every accessibility requirement.

A staging site is a separate environment used to build or review changes before they reach the public website. It helps the team review content, layouts, and functionality. Access, indexing, and deployment procedures should be planned so draft content does not become an unintended public version.

Booking, lead capture, and CRM connections can be scoped around the tools you use. We review their supported integration methods, licensing, required fields, and data flow. A useful integration also needs clear ownership of testing, error handling, and ongoing account access.

Yes. Bring your logo files, fonts, colors, and any existing guidelines. We can build within that identity and identify gaps that need attention without assuming you need a complete rebrand.

Content responsibilities are agreed during scoping. You may supply approved copy, work with us to refine existing material, or include writing in the project. Your team reviews factual details, service claims, and any examples before launch.

Not always. A business may benefit more from clearer messaging, a stronger typography system, better imagery, or consistent application of its existing identity. We assess what is already recognizable before recommending a change.

A practical handoff typically includes scalable vector artwork and common image formats, with appropriate color and background variations. Exact file types, versions, and usage guidance are defined in the agreed scope.

Yes. Your knowledge, customer questions, and approved examples provide the substance. Interviews, notes, or existing materials can become a starting point, with your team reviewing factual claims before publication.

Brand strategy defines who the business serves, the problem it solves, its position in the market, and how it should communicate. It gives design and content a shared direction. The output should be practical enough to guide website pages, campaigns, and everyday business materials.

A useful guide explains logo usage, colors, typography, imagery, and voice, with examples that reflect real applications. Depending on scope, it may also include layout patterns, social templates, or presentation guidance. It should help people apply the identity consistently.

Yes. A refresh can preserve recognizable elements while improving consistency, typography, messaging, or digital usability. The first step is identifying which elements customers already associate with the business and which parts are creating confusion.

Original photography can show the real people, work, products, and environment behind a business. Stock or illustrative imagery can still be appropriate when used honestly. The choice should reflect the story, available budget, and whether the image needs to demonstrate something specific about the company.

Start with the questions customers ask, the services you want to explain, and the decisions readers need to make. Search research can help identify language and demand, while sales and support conversations reveal practical gaps. Each topic should have a useful purpose and a relevant next step.

Only if the business can sustain useful material and review it properly. Improving a few important service pages may be more valuable than producing a large volume of repetitive posts. Frequency should follow the content strategy and available expertise.

AI tools can help with brainstorming, organization, and drafts, but business facts, examples, and final claims need human review. Content should reflect real expertise and be checked for accuracy, originality, and usefulness. Generated material should never invent testimonials, projects, or results.

No. Search positions depend on competition, search intent, your website, and systems outside any agency’s control. We focus on specific improvements, clear priorities, and honest measurement rather than ranking guarantees.

Only when the page can provide useful, distinct information for that audience. A list of city names is not a substitute for relevant content. We consider your actual coverage, services, and available evidence before expanding the location structure.

SEO improves how relevant pages can be discovered and understood in organic search. Local SEO focuses on location-related intent, business information, and genuine service coverage. The right mix depends on whether customers search for a nearby provider, a specialized service, or both.

Timing varies with competition, the starting condition of the website, the work involved, and how search systems respond. Technical fixes and content changes do not all produce the same effect. Progress should be reviewed over a meaningful period with relevant visibility, traffic, and business actions in context.

Technical SEO addresses how a site can be accessed, crawled, rendered, and understood. Typical areas include status codes, internal links, sitemaps, canonical URLs, page structure, and performance. It supports useful content; it does not replace it.

A title tag describes the page in browser tabs and may be used as the search-result title. A meta description summarizes the page and may appear as the snippet. Search engines can choose different text, so these fields should accurately represent the content rather than promise a fixed display.

Structured data describes page entities in a machine-readable format, commonly JSON-LD. It should match visible information and use the correct schema types. Valid markup does not guarantee rankings, inclusion, or a particular search appearance.

No. Google retired FAQ rich results beginning May 7, 2026. FAQPage markup can still describe an FAQ page, but it cannot guarantee an expanded Google listing. The priority is useful answers, clear page structure, accurate markup, and crawlable content.

llms.txt is a proposed Markdown reference file that points AI tools toward useful website information. It can summarize a business and link to authoritative pages, but it is not a replacement for robots.txt, a sitemap, or the website itself. Publishing it does not guarantee AI citations or better rankings.

Publish clear, accurate pages that answer real questions and make the business, services, and evidence easy to understand. Keep important information consistent and accessible, and maintain useful internal links. No agency can control whether a specific AI system cites or recommends a business.

robots.txt communicates crawling rules to compatible crawlers. A sitemap lists URLs for discovery. llms.txt is an optional descriptive guide for AI tools. These files serve different purposes and do not override authentication, indexing controls, or the need for useful public pages.

No. A page should describe genuine service coverage without inventing a local office, address, staff, or client history. Bocivus service-area pages describe markets for remote collaboration. Physical-location claims should be used only when they are accurate and supported.

Prioritize useful content and genuine mentions over volume. Purchased links intended to manipulate rankings and repetitive pages created primarily to capture search traffic can conflict with search-engine policies. Expansion should follow real services, relevant audiences, and information worth publishing.

No. The right mix depends on your audience, goals, budget, and ability to follow up. Starting with a focused set of activities makes it easier to learn what is working before expanding.

Media spend and agency work are separate items unless your proposal explicitly states otherwise. The proposal should explain campaign setup, ongoing management, creative deliverables, and who pays the advertising platform.

Pay-per-click describes a pricing model in which an advertiser pays for a click, commonly used in search advertising. A campaign still needs relevant targeting, creative, a useful landing page, and measurement. Click volume alone does not establish whether the campaign brings valuable customers.

Start with the business objective, audience, offer, geographic coverage, and the amount of learning needed. Media spend should be considered separately from creative and management costs. The initial plan should establish limits and a review process rather than assume an immediate return.

Search ads can reach people expressing an active need, while social campaigns can introduce an offer to selected audiences. The best choice depends on the product, buying process, creative, and available budget. A focused test is often more informative than launching everywhere at once.

A dedicated page can continue the specific message and offer in the ad, reducing the effort needed to understand the next step. It is especially useful when the homepage serves many audiences. The page should answer the campaign’s key questions and make the intended action clear.

Remarketing uses eligible audience signals to reconnect with people who have interacted with a business. Availability depends on the platform, audience size, consent choices, and applicable policies. It should be planned as part of a wider customer journey rather than treated as automatic permission to target everyone.

Possible causes include a mismatch between the audience and offer, weak landing-page clarity, form friction, or tracking problems. Review the full path from ad to inquiry and assess lead quality. More clicks are only useful when they support the intended business outcome.

Account ownership, billing, permissions, and access at the end of the engagement should be stated in the agreement. Businesses benefit from understanding which account holds their history and assets. Ask for clear access responsibilities before campaign work begins.

Creative should be reviewed when performance, audience response, or the offer changes. Replacing ads on a fixed schedule without enough evidence can obscure what is working. A testing plan should define which elements change and how the comparison will be assessed.

Publishing, community management, and customer service are different responsibilities. We define what is included, who responds to inquiries, and how sensitive or time-critical messages should be routed.

Automated welcome or follow-up sequences can be included when the platform and customer journey support them. We define the trigger, timing, content, and exit conditions so the sequence has a clear purpose.

Choose platforms based on where your audience pays attention and the type of useful content your business can produce. A professional service, local shop, and ecommerce brand may need different approaches. Consistency on a few relevant channels is often more practical than maintaining every platform.

Organic social can support recognition, trust, and customer relationships, but its reach is not predictable. It works best alongside a website and other ways for people to find and contact the business. Paid distribution may be useful for specific objectives when it is properly scoped.

A content calendar organizes topics, formats, publishing dates, and approval responsibilities. It helps the team coordinate useful material and avoid last-minute decisions. It should leave room for timely updates instead of becoming a rigid list of posts.

Purchased followers rarely demonstrate genuine interest, and purchased contact lists can create consent, deliverability, and platform-policy problems. Build an audience through relevant content and clear opt-in opportunities. Evaluate engagement and business outcomes rather than the size of a list alone.

A welcome sequence is a planned series of messages for a new subscriber or customer. It can introduce the business, explain what to expect, and offer useful next steps. The content and timing should reflect why the person joined the list.

Segmentation groups contacts by relevant information such as interests, relationship stage, or purchase history. It helps avoid sending every message to everyone. The available data, consent, and platform capabilities determine which segments are appropriate.

Look at delivery, meaningful clicks, unsubscribes, and the actions connected to the campaign’s goal. Open rates can be affected by privacy features and should not be treated as an exact count of readers. Compare results with the audience and purpose of the message in mind.

Automation can organize routine messages and route inquiries, but it does not replace a useful human response when a customer needs help. Define when an automated sequence should stop and who takes responsibility for the next conversation.

A large sample is important for reliable controlled experiments, but clarity and usability can be reviewed at any traffic level. We distinguish observations and recommendations from results that have been validated through testing.

Different tools count different events. Consent choices, blocked scripts, repeat submissions, spam, and attribution rules can all affect totals. We review the definitions and tracking setup before treating a difference as a business trend.

Choose metrics that connect to the business goal, such as qualified inquiries, purchases, booked appointments, or retention. Supporting measures such as traffic and engagement help explain the journey. A report is more useful when it distinguishes activity from outcomes.

A conversion is an action you define as valuable, such as a completed contact form or purchase. The definition should be explicit and measured consistently. Not every click or page view should be counted as an equally important conversion.

A lead is an inquiry or contact showing some interest. A qualified lead meets criteria relevant to the business, such as service fit, location, timing, or budget. Those criteria need agreement between marketing and the people handling follow-up.

Attribution describes how a system assigns credit to marketing interactions before an outcome. Different tools and models can report different contributions, and some activity cannot be observed. Treat attribution as a decision aid with limitations rather than a complete record of why someone bought.

A/B testing compares alternatives under a controlled setup to understand their effect on a defined outcome. Reliable interpretation depends on sample size, implementation, and how the test is run. A small fluctuation is not automatically evidence that one design is better.

A useful report explains the goal, relevant results, changes over time, important limitations, and recommended next actions. It should provide context for unusual events and distinguish observations from hypotheses. A dashboard full of numbers is not the same as an interpretation.

That can be scoped through form fields, CRM integration, campaign information, and agreed lead stages. The sales team needs a consistent way to record outcomes. Access, data quality, and privacy requirements influence how complete that connection can be.

It can include research, message clarity, navigation, form usability, landing-page improvements, and testing. The work begins with a specific problem or opportunity. Recommendations should distinguish usability findings from changes supported by a controlled experiment.

Catalog size, product variations, subscriptions, shipping rules, tax configuration, inventory connections, and content migration can all affect the work. We review the required purchasing and fulfillment flows before estimating the project.

Include clear product details, useful imagery, price, available options, and information that affects the purchase decision. Delivery, returns, sizing, compatibility, or care instructions may also matter. The page should answer the questions that would otherwise prevent a confident purchase.

Store migration can be planned after reviewing products, customers, orders, media, URLs, and platform constraints. Sensitive data and payment information require careful handling through supported methods. The scope should explain what can move, what cannot, and how the new store will be checked.

Choose methods supported by the platform and payment provider that suit your customers and operational needs. Fees, settlement timing, region, and risk controls matter alongside convenience. Payment-provider setup and approval are separate from visual website design.

Connections depend on the systems, available integrations, and the rules your business uses. We review product identifiers, stock updates, shipping logic, and error handling before estimating. Testing should include ordinary orders and relevant exceptions.

Common obstacles include unexpected costs, unclear delivery information, account requirements, form friction, and limited payment options. Some shoppers are simply comparing options. Analytics and usability review can help prioritize likely issues without assuming every abandoned cart has the same cause.

Subscriptions and memberships can be supported when the platform and payment tools fit the requirements. Renewal rules, access, cancellations, failed payments, and customer communication need to be defined. These features should be scoped beyond a standard one-time checkout.

Descriptions should help customers understand the actual product and how to choose it. Supplier text may miss important details or sound identical across many stores. Original, accurate explanations can be more useful than adding words solely to make a page longer.

The plan should cover products, variants, cart behavior, checkout, payment-provider test flows, order messages, and relevant shipping or tax configuration. The exact tests depend on the store. Live financial transactions should only be performed through an explicitly agreed process.

We review the handoff and ongoing responsibilities, including editing, hosting, maintenance, and future requests. Website care and ongoing marketing can be scoped separately so you know what support is included.

The amount and type of work depend on the selected plan. Your agreement should define included tasks, request limits, response expectations, and how larger development work is estimated.

It can if DNS records are changed without accounting for email. Before a migration, the plan should identify existing website and email services, preserve required records, and define how the transition will be checked.

A domain is the address people use to find the website. Hosting provides the environment that serves its files and application. They can be supplied by different providers, so renewal dates, access, and support responsibilities should be documented for each.

Your business should understand which account owns the registration, who can manage it, and how renewal is handled. Keep the registrant and recovery information current. An agency can assist with technical work without leaving ownership and access unclear.

A usable backup needs the files and data required to restore the site, with a clear storage location and recovery procedure. The appropriate frequency depends on how often important content changes. A backup plan is stronger when restoration is periodically checked.

WordPress, themes, and plugins change over time, and updates can affect compatibility or site behavior. Maintenance includes reviewing updates, preserving recovery options, and checking important functionality. The exact frequency and response expectations belong in the care agreement.

No. Security work reduces risk but cannot eliminate it. Updates, appropriate access, backups, monitoring, and reliable hosting are parts of a layered approach. Incident response and recovery responsibilities should be discussed before a problem occurs.

The agreement should describe the handoff of accounts, website files, assets, licenses, and ongoing services. Some third-party licenses or subscriptions may need to be transferred or replaced. Resolve ownership and exit terms before the engagement begins.

License terms vary by product and agreement. Some tools require recurring payment, and an agency license may depend on an active service relationship. Your proposal and handoff should identify which subscriptions are included and which your business must maintain.

An existing site can be reviewed to understand its platform, access, code, plugins, and condition. Support may require an initial assessment or cleanup before an ongoing plan is appropriate. We define any constraints before committing to maintenance responsibilities.