Straight answers about the work — and what we will not invent.

Regional SEO is about a metro or a multi-city area: maps, a Google Business Profile that matches how you serve that area, and pages with real regional substance — not a page for every ZIP. National SEO is about queries that do not name a place. You compete on topical authority and a site that can be crawled at scale. A national brand may still keep a few real office pages. That is support, not a find-and-replace of the regional playbook.

When customers visit or call a specific store, clinic, or office. That is multi-location SEO. Each distinct place needs an indexable location page, a listing, and NAP — name, address, and phone — that is identical everywhere it appears. A homepage that lists cities in the footer is not a location system.

Search engines verify a business by comparing name, address, and phone across your site, Google Business Profile, and directories. “Main St.” on one listing and “Main Street, Suite 200” on another looks like two records. Identical formatting is what confirms one entity at that address.

Complete NAP, unique copy about that site, services or hours that differ, a map embed, structured data, and a call to action for that location. Unique content is how you avoid a stack of duplicate city pages.

It shares location pages and listings. Franchise SEO adds territory rules and two layers of search: brand-level queries that should stay on the corporate site, and location-level “near me” queries that should hit the unit. Measurement has to split those views. A rising brand term does not mean a new franchisee is getting direction requests.

Usually no, not in a market that already has a corporate location page. Two sites for the same brand and city split authority — Google sees two entities claiming the same place. Franchisees still need accurate listings and a way to update local details. That does not require a competing domain. An indexable locations directory (typically /locations/) should list every unit and link to its page.

Yes. The same paragraph on fifty city pages is a quality problem and a ranking problem. Unique does not mean a different brand voice. It means true local detail so units do not cannibalize each other and only the flagship ranks.

A business website sells an inquiry: services, trust, locations, contact. An ecommerce storefront sells SKUs: product management, inventory, category architecture, and checkout. Ecommerce SEO follows the catalog. Brochure work is service and trust pages. Store work is taxonomy, product detail, and crawl control.

Filter panels (size, color, price, brand) can generate huge numbers of URL combinations. Most are near-duplicates of a category. Crawlers will only fetch so many pages. If they spend that budget on filter combinations, they fetch fewer of the category and product pages that can rank and convert. Index only combinations with real demand and enough products; canonicalize or noindex the rest.

Only if the platform can hold a real catalog and checkout. Often the information architecture has to be redesigned. Mixing a brochure and a store without a catalog plan usually produces a weak version of both.

The one your team can maintain and that can output crawlable pages. Next.js gives server rendering and control when you have developers. WordPress is strong for editorial teams and a short, disciplined plugin list. Webflow fits marketing teams that need to ship pages without a ticket. HTML is enough for a small, stable site. Wix and Squarespace are honest choices for speed-to-launch and polished templates. None of them ranks by logo. Hidden content, junk facet URLs, and a site nobody updates will lose on any stack.

Only if it cannot support the search or storefront brief. Staying is often right when the team already publishes there and the limits are acceptable. We do not trash Wix, Squarespace, or WordPress to sell a rebuild.

When the site is closer to a product than a brochure — custom data, server-rendered templates, or a team that will keep a repository. If marketers must ship landing pages every week without a deploy, Webflow is usually the better fit. If editors already live in wp-admin, WordPress is often the cheaper honest choice.

SEO is ongoing work, not a launch date with a guaranteed ranking. Early phases are usually discovery, a written plan, and the technical or listing fixes the plan named. Visibility on competitive queries takes longer than publishing a page. We will tell you what we will ship first. We will not invent a month when “results arrive,” and we will not quote another firm’s 3–6 month claim as if it were ours.

It depends on page count, platform, catalog size, and how fast you review. A small HTML or builder site is a different calendar from a multi-location directory or a store with facet rules. We scope that after we see the brief — not with a one-size number on this page.

No. We read messages at [email protected] during business hours. We will not publish a “we reply in X hours” promise we have not committed to.

The current site URL, what you sell, how many physical locations you operate (if any), whether franchisees have their own domains, the platform you are on, and whether this is a brochure or a catalog. Access to analytics or Google Business Profiles helps; it is not required to start the conversation.

For a design engagement, yes — or a decision that we will work with what you have. We will not invent a team photo, a founding year, or a testimonial to fill a layout.

Someone who can describe how you sell and who can approve IA or territory rules. For franchise work, corporate and a unit owner often need to hear the same domain recommendation.

No. We take regional through national engagements across the United States. A headquarters city is not required. We publish market pages for Los Angeles, San Francisco, New York, Chicago, Miami, Nashville, and Seattle.

Yes. That is usually multi-location or franchise SEO, sometimes with national work on the brand site. The plan follows the footprint, not a single ZIP.

Yes. This site, the contact form, and the engagement can run in English or Español. The process is the same: Discover, Strategy, Build/Optimize, Measure. The work does not get thinner in the second language.

Yes. We build English and Spanish routes when that is in the brief. Say so on the form so the IA includes both.