Evidence boundary
What is real, and what is withheld?
The sitemap, page types, production features, and live technical audit come from a real Teqri client website. The client name and historical commercial terms are omitted from this page. The budget and schedule below are current equivalents for reproducing the documented scope, not reconstructed claims about a private invoice.
Verified historical output
Public page system
Twenty-four live URLs cover the business, its three stores, and five meaningful product categories at each store. The audit checks the deployed pages directly.
Withheld private record
Client and original fee
No private contract, invoice, launch duration, traffic report, or revenue figure is disclosed. That protects the client and prevents invented precision.
Current comparable record
Public price and schedule
Teqri’s published Growth and Scale plans supply the current budget band. The four-to-six-week schedule is a current delivery plan for the same content-ready scope.
Page architecture
What was included in the 24-page scope?
The site is not 24 unrelated pages. It is a three-level customer path: understand the brand, choose a real store, then evaluate a category at that store.
| Page group | Count | Customer job | Primary content | Main action |
|---|---|---|---|---|
| Brand and utility | 6 | Understand the business and find the correct next path. | Brand promise, locations, story, team, employment, contact. | Choose a location or contact the business. |
| Location pages | 3 | Confirm a real store before traveling. | Address, phone, directions, store context, category links. | Call or get directions. |
| Location-category pages | 15 | Evaluate whether the nearest store is relevant to a product intent. | Category explanation, store facts, age language, contact path. | Visit or call the specific store. |
The 15 local pages have a real-world basis: three physical storefronts × five meaningful categories. Teqri did not add nearby city pages for places without a store merely to increase the indexable URL count.
Functional scope
Which features made the site useful?
The scope prioritizes store visits and factual discovery. It does not claim live inventory or ecommerce where the website cannot verify stock.
01 / Store discovery
Location-first navigation
A visitor can compare the three real stores, open the relevant location page, call, or get directions without searching the site manually.
02 / Mobile action
Calls and directions
Phone and map actions are designed for the device customers use while deciding where to visit.
03 / Category discovery
Useful, bounded pages
Each category page explains a real retail category and ties it to one storefront without asserting current inventory.
04 / Search foundation
Unique page signals
Every URL has a page-specific title, description, canonical, H1, and structured-data block.
05 / Compliance inputs
Client-directed controls
Age language and business notices are implemented from client-approved facts. Teqri does not independently provide legal or product-compliance advice.
06 / Ongoing care
One technical owner
Hosting, security, content requests, location changes, and technical support remain connected after launch.
Current reproduction plan
How long would the same 24-page scope take now?
With approved business facts, usable brand assets, timely reviews, and no ecommerce or custom application, Teqri would plan four to six weeks. This is a current schedule for reproducing the documented result; the original private elapsed schedule is not published.
Inventory and architecture
Confirm locations, categories, page list, calls to action, content sources, domain access, and measurement plan.
Design system and primary templates
Build the mobile navigation, homepage direction, location pattern, category pattern, forms, and component rules.
Brand and location pages
Complete the six brand/utility pages and three store pages using approved facts, photos, addresses, and phone numbers.
Fifteen local category pages
Produce page-specific content, metadata, headings, internal links, and store context without unsupported inventory claims.
Technical QA and review
Test responsive layouts, forms, links, structured data, accessibility basics, canonical URLs, redirects, and sitemap coverage.
Launch and observation
Publish, verify production responses and metadata, submit the sitemap, watch errors, and correct launch defects.
The schedule assumes the client supplies correct location facts and responds at review points. Photography, copy approval delays, ecommerce, third-party inventory feeds, legal review, or a rebrand can extend it.
Current public equivalent
What is the budget range for this website?
The historical client fee is private. Under Teqri’s public September 2026 plans, the same 24-page count fits Growth at $50 per month. Scale at $129 per month is the comparable upper band when the engagement needs unlimited pages, priority changes, or deeper customizations.
| Budget path | Monthly | 12 months | Why it fits | Boundary |
|---|---|---|---|---|
| Growth | $50 | $600 | Up to 30 pages, ongoing content updates, and search foundations. | Best when page count stays within 30 and the change queue is routine. |
| Scale | $129 | $1,548 | Unlimited pages, priority changes, maintenance, support, and customizations within plan scope. | Custom applications, ecommerce, or large integrations still require written scope. |
| Managed-provider sample median | $150 | $1,800 | Median across 26 public managed subscriptions in Teqri’s 2026 benchmark. | Providers differ in pages, copy, SEO, ownership, terms, and support. |
This is not the client’s invoice. It is a current public plan comparison for an equivalent page count and care model. Read the 50-provider pricing methodology and dataset before treating any starting price as a like-for-like quote.
Measured September 1, 2026
What did the live-site audit verify?
The production sitemap contained 24 URLs. Teqri fetched every URL and checked the response plus the basic signals that help a search system identify and distinguish each page.
Measured outcome: one complete, crawlable 24-URL system with page-specific titles and descriptions, self-consistent canonicals, primary headings, and structured data. This is a launch-quality result that can be rechecked; it is not a proxy for leads or revenue.
Claim boundary
What does this case study not prove?
Technical completeness is necessary for search visibility, but it does not guarantee a position, an AI citation, a visit, or a sale.
No ranking claim
Search results are competitive
A page can be indexable and still need stronger authority, links, reviews, engagement, or content to rank for a query.
No traffic claim
Analytics were not published
This page does not disclose Search Console clicks, sessions, or before-and-after traffic because those client records are private.
No revenue claim
Business attribution needs evidence
Calls, directions, store visits, and sales require agreed conversion tracking and business data over a defined period.
Project questions
24-page website cost FAQ
Is this a real Teqri website project?
Yes. The page architecture and September 1, 2026 live-site audit describe a real Teqri-built website for a three-location specialty retailer. The client name and private commercial terms are withheld in this cost breakdown.
How much would a comparable 24-page Teqri website cost now?
A 24-page scope fits Teqri's public Growth page limit at $50 per month, or $600 for 12 months. If it requires unlimited pages, priority changes, or custom work covered by Scale, the public equivalent is $129 per month, or $1,548 for 12 months. These are current plan equivalents, not disclosure of the client's historical fee.
How long does a 24-page multi-location website take?
Teqri would schedule a comparable, content-ready 24-page rebuild for approximately four to six weeks: architecture, design system, brand and location pages, local category pages, quality assurance, and launch. The original project's private elapsed schedule is not published.
What measurable result did the project achieve?
On September 1, 2026, all 24 sitemap URLs returned HTTP 200, all 24 had unique page titles and unique meta descriptions, all declared matching canonical URLs, and every page had an H1 and JSON-LD. No traffic, revenue, lead, or ranking claim is made without client analytics.
Why are there 15 location-category pages?
The retailer has three physical locations and five meaningful product categories per location. Each of the 15 pages combines a real store and a real customer intent rather than publishing thin city pages for places without a storefront.
Does this case study prove higher Google rankings?
No. The audit proves crawlable URLs, unique metadata, canonical consistency, headings, and structured data at a point in time. Rankings and business outcomes require Search Console, analytics, and revenue or lead data over a defined comparison period.