--- title: "Web development" description: "Web development from ShoutRank: pages and templates built so a crawler can fetch them and an answer can quote them. SEO, AEO, GEO, and AIO from the first HTML." canonical: https://shoutrank.com/web-development markdown: https://shoutrank.com/web-development.md --- # Web development Web development from ShoutRank: pages and templates built so a crawler can fetch them and an answer can quote them. SEO, AEO, GEO, and AIO from the first HTML. Web development at ShoutRank is the building of templates and pages whose HTML a crawler can fetch and whose opening an answer can quote. A search program that stops at a document does not change the site. When you need the page built, we build it: the template, the fields, the metadata, and the internal links. When your developers already own the repo, we specify the change and check the HTML after they ship. This is not a redesign sold on a mood. It is the URL model. Which pages exist, which canonicalize, and what the first screen says. A replatform that another team already owns is a [migration](https://shoutrank.com/seo-migration), not a second build. ShoutRank does not guarantee a ranking or a citation. ## The problem ### The design ships without a URL model. Templates launch, then SEO is asked which of the new URLs should rank. The index already has three versions of the same page. ### The important text is not in the HTML. The offer sits in a client-rendered block, an image, or a widget. The person sees it. The crawler and the answer do not. ### The marketing site and the product disagree. A new page names a feature the product no longer sells, or hides the limit that would have made the page citable. ## How ShoutRank approaches it We write the page types first: what gets a URL, what is a field on a template, and what must be in the first HTML response. Then we build, or we hand that spec to the team that builds. After release we fetch the URL the way the [visibility audit](https://shoutrank.com/visibility-audit) does. A screenshot of the design is not evidence that the document is indexable. ## What the work includes ### URL model The page types that may exist, and the ones that should canonicalize or stay out of the index. ### Templates Metadata, headings, internal links, and the fields an editor can change without breaking the structure. ### HTML check A fetch of the priority URLs after they ship, including what a bot receives before JavaScript. ### Editor notes How to add the next page without minting a duplicate. ## Process ### Discovery List the queries and the page types that should own them. ### Audit Read the current templates, the repo or CMS, and who is allowed to ship. ### Strategy Decide what ShoutRank builds and what your developers build. ### Implementation Ship the templates with indexation, canonicals, and the opening passage in the HTML. ### Monitoring Fetch the URLs after release and log rankings separately from citations. ### Optimization Fix the template when a new page type starts splitting one query. ### Reporting What exists, what is indexable, and what an answer can lift from the opening. ## Why ShoutRank ### Search is in the build A page written for an answer and then pasted into a template that hides the text does not get cited. ### We can sit beside your developers Technical SEO on this site says we do not replace a team that already ships. Web development is the engagement when you need the pages built. ### English, on a stack you can keep We build in the CMS or framework the company will still be able to edit. We do not leave a site only we can change. ## How success is measured Whether the priority URLs return indexable HTML with the assigned title and canonical. Non-brand impressions on those templates after they ship. Whether chat answers and AI Overviews can lift the opening, checked on a fixed set. We do not invent a conversion lift. A named client result is published when that client clears the figure. Until then the report is the measurement. ## Questions ### Do you rebuild whole sites? When the URL model is the project, yes. When another team is already replatforming, we join as the migration review instead of starting a second build. ### Which stacks do you work in? The one you can maintain. WordPress, Webflow, Shopify, and Next.js are the usual ones, and each has its own notes on this site. An unusual stack is a conversation, not a silent yes. ### Is web development separate from SEO? The invoice can be. The page cannot. A template that is not fetchable is not finished, even if the design was approved. ## Related - [Technical SEO](https://shoutrank.com/technical-seo): When the site exists and the HTML is the problem. - [SEO migration](https://shoutrank.com/seo-migration): When the new site is already someone else’s project. - [Next.js](https://shoutrank.com/nextjs-seo): When the document a crawler receives is a rendering choice.