Skip to content
Website Development in 2027: The Build and Audit Checklist

Website Development in 2027: The Build and Audit Checklist

Balaji Naidu avatarBalaji Naidu22 min read

In short

  • Build for four readers at once: a person on a phone, Google, AI crawlers, and an AI assistant that may quote one paragraph of your page.
  • Most losses are plain failures: a broken sitemap, a form that loses a message, a claim the live site does not support. Check those before anything clever.
  • Test every point yourself. Each rule below ends with a check that takes under five minutes.

Most advice about websites in 2027 says "AI changes everything." It does not. What changed is who reads your site, and that is a short list you can design for.

This post is a checklist. Each rule is short. Each one ends with a check you can run in five minutes. Where we know something from public documentation, we say so. Where it is our judgment, we say that too. Where nobody knows yet, we say that.

We start with our own mistakes, because they are the most useful part.

What we found when we checked our own work

On 4 November 2026 we opened the seven websites WebMarv had built for clients. We looked at each one the way a buyer or a crawler would: in a real browser, and as raw HTML. We compared what we found with what we had written about each project.

  • Four of seven had a sitemap or robots.txt that was missing, returned a 404, or returned the app's own page instead of a file.
  • Two had no structured data, although our case studies said they did.
  • Two were described wrongly in our case studies. One was a different kind of business than we had written. In the other, the audience was wrong.
  • Two of seven matched what we had published with no defect: a hospital site with 270 pages in two languages, and a small travel booking site.

Some sites appear in more than one line. Five of the seven had at least one defect.

We took one case study down and corrected others. We do not name the clients here, because the fixes are theirs to make.

Nothing on that list is advanced. Nobody had checked after launch. That is the whole lesson, and it is why this checklist ends with upkeep.

Three more findings from our own site, from Search Console in the 28 days to early November 2026:

  • Pages for India drew 1,141 impressions and 51 clicks. The 28 days before that drew 32 impressions and 2 clicks. The work we did helped, from a very low start.
  • One page aimed at the UK drew 29,882 impressions and 1 click. Impressions are not demand. We took our country and city pages out of search.
  • The pages in positions 2 to 5 were all brand searches. Searches for what we sell sat between positions 20 and 70. A good brand position says people know you. It says nothing about whether strangers find you.

One more, about a form. Our contact form saved a "duplicate" marker before the email was sent. If the send failed, the visitor's retry was blocked as a duplicate. We now save the marker only after a successful send, and the form returns an error when mail is not configured.

Who reads your website now

Design for these five, in this order.

ReaderWhat it needsHow it fails
A person on a phoneThe answer, the price range, a way to call or messageSlow page, popup, long form
GooglebotCrawlable, indexable pages with clear titlesBlocked, duplicated, or thin pages
AI crawlersPlain HTML text, allowed in robots.txtText that only appears after JavaScript runs
An AI assistant answering a buyerA short, specific, checkable passageVague claims, facts that differ across sites
The buyer who checks youProof that holds up when openedA claim the live site does not support

Check: open your homepage with scripts off. Whatever you can still read is what the weakest crawler sees.

What is still true

  • A fast page beats a slow page.
  • A clear title and a clear first paragraph beat a clever one.
  • Pages that answer a real question get found. Pages written for a keyword do not.
  • A phone number that works is worth more than a new design.
  • Other sites that talk about you, and agree with each other, still matter more than anything you say about yourself.

What you can drop

  • Heavy animation and parallax that add seconds to load time.
  • A hero video that autoplays and says nothing.
  • An About page with no names, dates or places.
  • One page per city with the same text and the city name swapped.
  • Blog posts written to hit a word count.
  • Stock photos of people shaking hands.
  • "Leading provider" language. A crawler cannot extract a fact from it, and a buyer stops reading.

Decide these before you build

Rule 1. Write the one question the site must answer

Write it the way a buyer would type or say it. Example: "Who builds a bilingual hospital website that takes appointments on WhatsApp?" Every page should help answer one such question.

Check: ask three real buyers what they asked before they found you. Use their words.

Rule 2. State your facts once, then copy them exactly

Legal name, address, phone, hours, founders, year founded. Write them once in a single file. Use that file everywhere: site, Google Business Profile, directories, social profiles.

AI systems and search engines trust what several sources agree on. If your hours differ between two places, you are asking them to guess.

Check: search your business name and phone number. Compare every result with your master file.

Rule 3. Put readable text in the HTML

Server-rendered or static pages put the text in the first response. Pages that build their text in the browser depend on the crawler running scripts. Google does. Studies we have seen suggest several AI crawlers do not. Do not bet on it.

Check: run curl https://yoursite.com/service-page and read the output. If your text is missing, a crawler may not see it.

Rule 4. Fewer pages, each with one job

Start with: home, one page per service, pricing, proof, contact, and a page where a buyer can check you. Add a page only when a real question needs it.

Check: list every page and write its single job in one line. If two pages share a line, merge them.

Rule 5. Choose the URL shape now

Short, readable, lowercase, words separated by hyphens. Changing a URL later means a redirect for life.

Check: read your URL aloud. If you cannot, shorten it.

Content rules

Rule 6. Answer first

Open every page with a direct answer of 40 to 60 words. Then the detail. A person gets the answer in five seconds. An assistant gets a passage it can quote.

Check: cover everything below the first paragraph. Does the page still answer its question?

Rule 7. Write what only you know

Your prices, your timelines, the jobs you refused, what went wrong last time. Anyone can write "we deliver quality." Only you can write "we turned down this project, and here is why."

Check: remove your name from the page. If a competitor could publish it unchanged, rewrite it.

Rule 8. Every claim needs proof a stranger can open

A claim with no proof comes out. A claim that the live work contradicts is worse than no claim. We learned this from the checks above.

Check: for each claim on a service page, name the link that proves it. If you cannot, delete the claim.

Rule 9. Say what you have not done

A short list of limits makes the rest believable. Ours says we have not yet deployed an AI voice agent for a paying client, and that most of our published work is in India. Assistants and buyers both give more weight to a source that states its limits.

Check: is there one sentence on your site that a salesperson would prefer you removed? If not, you are probably hiding something.

Rule 10. Publish prices as ranges

Show a starting price and what moves it. Buyers leave pages that hide cost. Assistants repeat the numbers they find.

Check: can a buyer tell, from your site alone, whether you are in their budget?

Rule 11. Case studies must survive a click

A live link, the date of the work, what was built, and how any result was measured. Show a number only when it comes from the client's own records. "In progress" is not a case study. A playbook that says what you would do and how you would measure it is more honest.

Check: visit each linked site on your phone. Is everything you wrote true on that site today?

Rule 12. Take FAQs from real buyers

Use WhatsApp messages, emails and call notes, with names removed. Keyword tools give you what people typed years ago. Your inbox gives you what they ask now.

Check: your first twenty FAQs should each come from a real message.

Rule 13. Date your pages

Show "last reviewed" on pages with prices, terms or claims. Set a reminder to review them. A price from 2024 on a 2027 page loses trust.

Check: sort your pages by last edit. Anything older than a year with a number in it needs a look.

Page order that works

For a service page, use this order. It works for people and it gives machines clear passages.

  1. Direct answer (40 to 60 words)
  2. Who it is for, and who it is not for
  3. Price range and what changes it
  4. How the work runs, step by step
  5. Proof: one or two real examples with links
  6. Limits: what we do not do
  7. Questions buyers ask
  8. How to contact us, with a phone number

Rule 14. Headings should make sense alone

An assistant may lift one section out of your page. A heading like "Our Approach" means nothing alone. "How a bilingual hospital site is built and priced" does.

Check: copy only your headings into a list. Can you tell what the page says?

Rule 15. Use tables and lists only when they help

Use a table to compare things. Use a list for steps or items. Do not turn ordinary paragraphs into bullet points to look organised.

Every important page should be reachable in a few clicks, with link text that says where it goes. Orphan pages, with no links in, may never be found. When we checked our own site we found eleven useful pages that no parent page linked to.

Check: crawl your site with any free crawler and list pages with zero incoming links.

Images, video and other files

Rule 17. Use real photos

Your team, your office, your work. Name the file clearly and write alt text that describes what is in the picture. Do not fill alt text with keywords.

Rule 18. Set image size and load order

Give every image a width and height so the page does not jump. Use a modern format such as WebP or AVIF. Do not lazy-load the main image at the top of the page. Mark it high priority instead.

Check: run PageSpeed Insights on your main pages. Read the largest-image item first.

Rule 19. Use video only when it shows something text cannot

No autoplay with sound. Add a transcript, so a crawler and a person without sound both get the content.

Rule 20. Cut third-party scripts

Chat widgets, trackers, font loaders and popups are the usual cause of slow pages. List every script, write down who asked for it, and remove any no one can justify.

Check: open the browser's network panel and sort by size. As a rough guide, any large file that is not your content needs a reason.

Rule 21. Publish a file people can cite

A dataset, a checklist, a price table. Sites link to things they can quote. A downloadable CSV with a stated method is more useful to a journalist than a blog post.

Experience on a phone

Rule 22. Make contact one tap away

A call button and a WhatsApp link on every page, visible without scrolling on a phone. In our experience in India, many buyers message before they call.

Check: on your own phone, can you start a call from any page in one tap?

Rule 23. Keep forms short

Name, phone or email, and one line about the need. Every extra field loses some people. Ask for the rest on the call.

Rule 24. Test that forms deliver

A form that looks fine and loses messages is the most expensive bug on a small business site. Check these four things:

  • The message reaches a real inbox.
  • If sending fails, the visitor sees an error and a phone number, not a thank-you.
  • A retry after a failure is allowed.
  • A second channel also alerts you, such as WhatsApp or a second email.

Check: submit your form every week. Put it in the calendar.

Rule 25. Reach Core Web Vitals targets in real use

Google's published "good" levels, measured at the 75th percentile of real visits, are: largest content shown in 2.5 seconds or less, interaction response of 200 milliseconds or less, and layout shift of 0.1 or less.

Lab tests help while building. Real-user data decides. A new site may have too little traffic for real-user data, so check again after a few weeks.

Check: PageSpeed Insights shows both lab and, where available, field data.

Rule 26. Meet the basic accessibility level

Readable text size and contrast, labels on form fields, buttons you can reach with a keyboard, and alt text. It helps people. It also gives machines cleaner structure.

Check: tab through the page with the keyboard only. Can you reach and use everything?

Use a small banner that does not cover the page. Do not block content until the visitor clicks. Do not load tracking before consent where the law requires consent.

SEO that still applies

Rule 28. Get the basics right

  • Every page you want found returns status 200 and is not blocked or marked noindex.
  • Each page has one canonical URL.
  • Your sitemap lists only real, indexable pages, and robots.txt points to it.
  • Redirects are single steps. Old URLs go to the closest new page.
  • Language tags such as hreflang are used only where real translated pages exist.

Check: open yoursite.com/robots.txt and yoursite.com/sitemap.xml. Both must return a real file, not your homepage and not an error. This was our most common failure.

Rule 29. Write titles for the click

Keep the title under about 60 characters. Put what the page is first, then who it is for. Write the description as one honest sentence, not a keyword list.

Rule 30. Mark up only what the page shows

Structured data tells machines what a page contains. Google's rule is that it must match the visible content. Add the type that is true: Organization, LocalBusiness, Service, Article, Person. Do not add a type for something the page does not show.

FAQ markup no longer gives most sites a special result in Google, since 2023. We still write FAQs because buyers read them. Do not add the markup expecting a visual reward.

Check: use Google's Rich Results Test and the Schema.org validator. Then read your own page and ask whether each marked-up fact is visible on it.

Rule 31. Treat local SEO as a facts problem

Claim your Google Business Profile. Set one primary category. Keep name, address and phone identical to your website. Ask real customers for specific reviews, spread over time. Never pay for reviews or write your own.

A city page works only if it has something true for that city: a real project, a real address, real local detail. Copied text with a different city name is thin content. We took ours out of search for that reason.

Links and mentions come from things worth citing: original data, a useful tool, a clear guide, a real client who links to you. Bought links and mass directory submissions can hurt more than help. Review your backlinks once a year. File a disavow only for a clear spam pattern or a manual action, not as routine.

Rule 33. Measure with Search Console first

Connect Search Console before launch. Look at four reports: pages indexed, queries, pages, and countries. Compare complete periods, such as 28 days against the previous 28 days.

Split brand searches from non-brand. Our own brand terms were in positions 1 to 5 while the terms we wanted were at 20 to 70. One average would have hidden that.

AI search: what is known, what is likely, what is unknown

Much of what is written about this is guesswork stated as fact. We separate it into three groups.

StatusStatement
DocumentedGoogle says its AI features in Search draw on the same index and need no special markup. A page must be indexable and eligible to show a snippet.
DocumentedEach AI company publishes the names of its crawlers, and honours robots.txt rules for them. Google separates Googlebot from Google-Extended, which controls use for its AI models.
DocumentedStructured data must match visible content.
Our judgmentShort, specific, self-contained passages get quoted more than long, vague ones. We have not measured this ourselves.
Our judgmentFacts that several independent sources agree on are more likely to be repeated.
UnknownWhether any major system reads llms.txt.
UnknownExactly how an assistant chooses which source to cite, and how often that choice changes.

For the longer background, see what answer engine optimization is, GEO and SEO compared, and how search results are changing.

Rule 34. Decide which bots you allow

There are three kinds: search bots that fetch pages so you can be found, bots that fetch a page when a user asks an assistant about it, and bots that collect content for model training. Allow the first two if you want to be found. Decide the third on principle.

Use the bot names each company publishes. A rule copied from a blog may be out of date.

Check: read your robots.txt. For each rule, can you say which bot it affects and why?

Rule 35. Add llms.txt if you like, expect little

It is a plain file listing your key facts and links. It takes an hour. We have not seen confirmation that Google or the main AI companies use it. Treat it as housekeeping, not a strategy.

Rule 36. Write passages that can be quoted

A quotable passage names the subject, gives the fact, and stands alone. Prefer "Every proposal states the delivery date and the payment schedule in writing" to "we move fast." The first can be checked. The second cannot.

Rule 37. Keep facts the same everywhere else

Assistants build their view of your business from many places. Your site, your Google profile, directories, press, and review sites should tell one story. A wrong detail on a directory page you forgot about can outweigh a perfect page of your own.

Check: every quarter, list the ten places that describe your business. Fix any that disagree.

Rule 38. Test monthly and keep dated records

Write ten questions a buyer would ask. Ask the same ten in the main assistants once a month. Record three things for each: were you mentioned, were you linked, were you recommended. Save the date and the full answer.

One answer proves nothing, because answers change between runs. Look at the trend over months. We have not published results for WebMarv yet. We will, with dates, when we have a set worth showing.

Trust

Rule 39. Give buyers a way to check you

One page with your registered name, address, how to look you up in the company registry, your Google profile, your public prices, your contract terms in plain words, and a list of what you have not done. See ours at Verify WebMarv.

Check: could a stranger confirm you exist and are what you say, in five minutes, without calling you?

Rule 40. Get reviews that are specific

Ask clients to say what you built and what it was like to work with you. In our view, eight specific reviews from real clients beat fifty vague ones. Ask for permission, give no reward, and do not write them yourself.

Rule 41. Offer reference calls

Three clients who will take a ten-minute call are worth more than any badge. Ask permission first, and show only what they approve.

Rule 42. Keep security and privacy basic and honest

HTTPS everywhere, security headers set, software updated, and a privacy policy that matches what the site collects. Collect only what you need. Do not log personal details in server logs.

Rule 43. Use AI to write only with a human check

AI tools are good for first drafts, outlines and cleaning grammar. They are bad at facts about your business. They produce the vague, even tone that readers and search systems learn to ignore. Every page needs a named person who checks each claim against a source before it is published.

Check: pick any sentence on your site. Can someone tell you where the fact came from?

Launch checklist

Run this before you go live. Copy it.

Crawl and read

  • Homepage and service pages readable with curl
  • robots.txt returns a real file and allows the bots you want
  • sitemap.xml returns a real file with only indexable URLs
  • No page you want found is marked noindex
  • One canonical URL for every page
  • Old URLs redirect in one step
  • No page returns 200 for something that does not exist

Content

  • Each page opens with a direct answer
  • Each claim has a link to proof
  • Prices shown as ranges with what changes them
  • A limits list is published
  • Name, address, phone, hours match everywhere
  • Pages show a review date

Experience

  • Call and WhatsApp buttons work on every page
  • Form tested: delivery, failure message, retry, second alert
  • Main image is not lazy-loaded and has set dimensions
  • Page speed checked on a phone
  • Keyboard test passed
  • Consent banner does not block content

Search and AI

  • Search Console connected and the sitemap submitted
  • Structured data validated and matches visible text
  • Google Business Profile claimed and consistent
  • AI test questions written and the first run saved
  • llms.txt added, if wanted

After launch: the first 90 days

  • Day 7: check that key pages are indexed. Fix any crawl errors. Test the form again.
  • Day 28: read Search Console for the first complete period. Note brand against non-brand. Change nothing big yet.
  • Day 56: compare against day 28. Improve pages that have impressions and few clicks, starting with their titles and first paragraphs.
  • Day 90: run the AI test set again. Compare with the first run. Decide what to write next from the real questions you received.

Do not rebuild in the first 30 days. The data is too thin to tell you anything.

Monthly upkeep

  • Submit the form and confirm it arrives.
  • Open your sitemap and robots.txt.
  • Check for broken links and pages that now return errors.
  • Check each case study link still shows what you wrote.
  • Review any page with a price or a date.
  • Run the AI test questions.

This is the step that would have caught four of our seven sitemap problems.

What nobody knows yet

  • How much buying will be done by software agents that visit sites for the buyer.
  • Whether assistants will keep citing small sites or lean on large ones.
  • Whether llms.txt, or something like it, becomes a standard.
  • How AI answers will treat paid placements.

The checklist above does not depend on any of these. A fast, readable, honest, checkable site works under each outcome.

When not to build all of this

A small local business with a single service may need only a fast one-page site, a claimed Google profile, a phone number, a WhatsApp link, and ten honest reviews. Do that first. Everything else is for when you have something to add.

If you want this checklist applied to your own site, send us the URL for a free audit. If your project is a poor fit, we will say so, as on our projects we turned down page. Prices and what changes them are on the website cost guide.

  • Website Development
  • Checklist
  • GEO
  • Technical SEO
  • AI Search
Balaji Naidu - Founder & Growth Engineer

Written by

Balaji Naidu

Founder & Growth Engineer

Balaji Naidu is the founder of WebMarv Innovations LLP. He connects business growth with digital systems — from search visibility and demand generation to conversion funnels and revenue attribution. He leads strategy, growth engineering, and business development.

  • Marketing & SEO
  • System Architecture
  • Next.js
  • Revenue Systems
  • Business Strategy
View founder profile & articles →

FAQ

Questions about this topic

Not answered here? Ask us directly.

Do I still need SEO if people use AI assistants?

Yes. Google's own guidance says its AI features use the same search index and need no special markup. If a page cannot be crawled, indexed and read, neither Google nor most AI systems can use it. SEO is now the base layer, not the whole job.

Should I add an llms.txt file?

It costs an hour and does no harm, so we add one. We have not seen confirmation from Google or the main AI companies that they read it, so do not expect results from it alone.

Should I block AI crawlers in robots.txt?

Decide by goal. If you want to be found and quoted, allow the search and answer bots. If you want to keep your content out of model training, you can block the training bots. Each company documents its own bot names. Check them before you copy a rule from a blog.

Is a JavaScript-only website a problem in 2027?

It can be. Google renders JavaScript, but studies we have seen suggest several AI crawlers do not run it. If the text only appears after scripts run, those crawlers may see an empty page. Test with curl and read what comes back.

How many pages should a new business website have?

As few as can each do one job: home, one page per service, pricing, proof, contact, and a page that lets a buyer check you. Add a page only when a real buyer question needs it. Pages that repeat the same text with a different city name hurt more than they help.

How do I know if AI assistants mention my business?

Ask the same ten questions a buyer would ask, once a month, in the main assistants. Record three things separately: mentioned, linked, and recommended. Save the date and the exact answer. One answer proves nothing, because answers change.

What does a website like this cost in India?

It depends on pages, languages, integrations and content work. Our public price ranges and what changes them are on the website cost guide.

WebMarv background pattern

Free audit

Want this done for you? Free audit.

“Our clients need to see deep technical capability across enterprise stacks. WebMarv built a 46-page modern site in two weeks that accurately reflects our scale and brings qualified enterprise leads every week.”

Executive Leadership·Leadership Team, Spiroware Infotech

Case study ↗
Step 1 of 4
Which solution do you need?
Tap an option to continue