What should a modern marketing website include?
A modern marketing website should include the pages, systems, and proof needed to turn anonymous traffic into qualified pipeline. That means a homepage that explains the category, product or service pages that answer high-intent searches, use-case pages that match role or industry, proof pages that reduce risk, comparison pages that capture decision-stage demand, and a contact or demo path that is easy to find.
At Virdis, we see the same pattern across real client work for Hona, Handoff, IndeHR, Torch Dental, MeterNet USA, and Aurora Lights. The sites that hold together are the ones where the sitemap, content model, analytics plan, and conversion path are decided before visual polish starts.
That lines up with our own analytics. In the last 90 days, the homepage drew 102 sessions and 35 engaged sessions with 2,039 seconds of engagement. That tells us buyers still start broad, then move into practical planning, setup, and evaluation content. Google’s own guidance also says a logical site structure helps users and search engines understand how pages relate to the rest of the site, and Ahrefs makes the same point about internal linking and navigation (Google Search Central, Ahrefs).
Use this page stack as the baseline:
| Site layer | SEO job | Conversion job |
|---|---|---|
| Homepage | Define category and positioning | Route visitors to the right path |
| Product or service pages | Rank for high-intent terms | Explain fit, value, proof, and next step |
| Use-case pages | Match role, industry, or workflow intent | Make relevance obvious to a specific buyer |
| Comparison pages | Capture bottom-of-funnel alternatives | Help buyers choose without a sales call |
| Case studies | Support trust and proof queries | Reduce risk before demo or contact |
| Blog and guides | Build topical authority | Move readers toward related commercial pages |
| Contact or demo pages | Capture demand | Remove friction from the handoff |
Related Virdis resources: B2B SaaS web design, Sanity CMS development, SaaS redesign framework, and Next.js vs Webflow for SaaS.
How should you structure the pages?
Structure the pages around buyer intent, not around departments or internal org charts. A good marketing site makes the customer journey obvious: who it is for, what problem it solves, what proof backs it up, and what the next step should be.
We usually start with a shallow hierarchy: homepage at the top, then service or product pages, then use-case pages, then proof and comparison content, then supporting articles. That structure keeps the crawl path simple and makes navigation easier for humans. It also gives search engines cleaner signals about which pages belong together.
A practical homepage order looks like this:
- Hero with category, target buyer, and one primary CTA.
- Proof strip with logos, metrics, or short credibility signals.
- Problem-to-outcome copy in plain language.
- Product or service explanation.
- Use-case routing by role, industry, or workflow.
- A proof section with case studies or results.
- Objection handling or comparison links.
- Final CTA tied to audit, demo, or consultation.
The same logic applies to deeper pages. A service page should not try to be a homepage. A use-case page should not become a generic feature dump. A comparison page should answer the buying question quickly and honestly. A case study should do the opposite of a vague testimonial: show the problem, the work, and the result.
This is also where content gaps show up. In the Search Console research that informed this topic, the site’s strongest impressions clustered around commercial and structural pages like services, use cases, and comparison content, while decision-stage pages were visible but under-clicked. That is a signal to improve page mapping and internal links, not just title tags.
For a clean page map, use this rule:
- Homepage → service pages, use cases, proof, contact
- Service pages → relevant use cases, case studies, and supporting guides
- Use-case pages → service page, proof, and one related article
- Comparison pages → alternatives, case studies, and contact
- Blog posts → one commercial page and one proof page
Avoid the common mistake of making the site flat and noisy. If every page links to everything, nothing feels important. If only the homepage links to the demo page, early-stage visitors get stranded. The right answer is selective routing.
What technical decisions matter before design starts?
The technical decisions matter because they determine whether the site is maintainable after launch. Design can make a site feel better. Structure and CMS decisions decide whether the team can keep shipping without creating chaos.
A modern marketing site should define these things early:
- URL patterns that are readable and stable.
- A CMS schema that matches the page types.
- Template rules for metadata, headings, and CTA placement.
- Analytics events for CTA clicks, form starts, form submissions, and booked meetings.
- Redirect rules for future migrations.
- Image and script constraints that keep the site lean.
- Schema markup for the page types that need it.
Google’s starter guide says search engines rely on links and page organization to understand content, and its documentation also emphasizes that duplicate content can waste crawl resources. Think with Google’s page speed research adds another warning: as mobile load time increases from one second to seven seconds, bounce probability rises sharply, and conversion probability drops as page complexity grows (Think with Google).
That matters for full-stack custom design and development. A custom stack is not automatically better, but it gives you control over the things that matter once the site becomes a growth channel: content modeling, performance, schema, tracking, and integration points. Webflow, Framer, Squarespace, and HubSpot CMS can be the right choice for smaller sites or simple campaigns. A custom build becomes worth it when the website needs structured publishing, multi-step conversion paths, and a CMS that can evolve with the business.
A practical technical checklist:
- Generate XML sitemaps for all indexable pages.
- Use canonical URLs on every template.
- Make headings and metadata structured fields, not free-form text.
- Track the actions that actually create pipeline.
- Keep the number of non-essential scripts low.
- Preserve redirects before redesigns launch.
- Compress images and avoid bloated hero sections.
- Add Article, Organization, BreadcrumbList, and relevant page schema where it helps.
This is the point where teams usually get the architecture right or break it. If the CMS schema is vague, authors will improvise. If the tracking plan is incomplete, no one will know which pages work. If the template system is too rigid, future content will feel hacked together.
How do you launch and measure the site?
Launch the site as a measurable system, not as a design reveal. A site is not finished when the pages look good in Figma or the browser. It is finished when the main journeys are live, tracked, and easy to improve.
Start by launching the pages that support the main buying path:
- Homepage.
- Core service or product pages.
- Top use-case pages.
- One or two proof pages.
- The main demo or contact page.
- The first supporting articles that feed those money pages.
Then measure whether people are moving through the site the way you intended. The signals that matter are not just pageviews. Track CTA clicks, form starts, form submits, booked calls, scroll depth on key pages, and which supporting articles send visitors into commercial pages.
This is where the architecture from the first section pays off. If the homepage is doing its job, it routes mixed-intent traffic. If the service pages are doing their job, they convert evaluators. If the blog is doing its job, it supports topic clusters and nudges people toward the right page.
During a MeterNet USA migration audit, we treated Core Web Vitals, redirect coverage, and priority-page preservation as launch criteria. That is the right mindset for every modern marketing site: preserve what already works, then improve the structure without breaking the paths that produce demand.
Keep an eye on the first two weeks after launch:
- Crawl errors
- Redirect loops or missing redirects
- Template bugs
- Missing metadata or schema
- Broken CTA paths
- Slow pages on mobile
- Pages with traffic but weak engagement
Google also notes that some changes can be reflected quickly while others take weeks or months to settle. That means the first publish is the beginning of the feedback loop, not the end of the project.
How should content fit into the website?
Content should support the website, not sit beside it. The strongest marketing sites are not just pretty shells. They are content systems with a clear relationship between educational pages and money pages.
We already see this on the Virdis side. The pages that attract engaged traffic are practical, not abstract: website planning, Google Tag Manager setup, website design, conversion rate optimization, and FAQ-style utility content. That tells us readers want tactical help. They want to understand how to build, audit, or fix the site they already have.
Build content clusters around actual buying decisions:
- Planning content: website structure, sitemap planning, redesign timing, launch checklist.
- Platform content: Next.js vs Webflow for SaaS, Next.js vs Framer, Next.js vs HubSpot CMS.
- Conversion content: landing page structure, demo page optimization, SaaS CRO.
- Technical content: Core Web Vitals, schema, CMS modeling, hosting choices.
- Proof content: migration notes, before-and-after architecture, case studies.
This is where internal links do the work. A planning article should point to a service page. A comparison article should point to a case study or contact page. A case study should point back to the relevant service page and use-case page. That gives the site a mesh instead of a pile.
The article you are reading should do the same thing. It should help a buyer understand the shape of the project, then point them to the next step.
Frequently asked questions
How many pages does a modern marketing website need?
A modern marketing website usually needs enough pages to cover the main buying paths, not a huge volume of thin content. For many B2B SaaS teams, that means a homepage, a few service or product pages, a few use-case pages, a proof section, one or two comparison pages, and the first handful of supporting articles.
Do I need a blog from day one?
You do not need a large blog from day one, but you do need a plan for educational content. If the blog has no relationship to service pages, it becomes noise. Start with a small cluster of pages that support the top commercial journeys and expand from there.
Should I build this on a visual builder or a custom stack?
Use a visual builder when speed and simplicity matter more than long-term structure. Use a custom full-stack setup when you need tighter control over content modeling, performance, analytics, and future scalability. The right answer is the one that matches the site’s job.
When should schema and tracking be added?
Add schema and tracking before launch, not after. If you wait, you lose baseline data and you risk shipping pages that cannot be measured correctly. Tracking should cover the actions that matter to pipeline, and schema should map to the page types you actually publish.
When is the site ready to launch?
The site is ready to launch when the major pages are live, the CTA paths work, the CMS is usable, the redirects are in place, the important pages are indexed, and the analytics events are firing. If the team cannot measure or maintain the site, it is not ready.
