To build a website better than a competitor's in 2027, compare both sites on six measurable points (field speed, a page per service and area, offer and proof on the first screen, forms, structured data, accessibility) and fix the points where you lose first. Google now measures responsiveness with INP, the EU accessibility rules have applied to online shops since June 2025, and Google's AI Mode reads your pages to answer local questions. Below are the dated changes, a comparison table with thresholds and a 90-day plan.
What changed for business websites by 2027
These facts from Google and regulators set the bar a competing site has to clear in 2027. Each line below has a date and the original source.
| Date | Change | Source | What it means for your site |
|---|---|---|---|
| 12 Mar 2024 | Interaction to Next Paint (INP) replaced First Input Delay as the responsiveness Core Web Vital | Google Search Central | Slow reactions to taps and clicks now show up in Search Console as a failed metric |
| Current | "Good" thresholds: LCP within 2.5 s, INP 200 ms or less, CLS 0.1 or less, at the 75th percentile, mobile and desktop counted separately | web.dev | The target for every template on the site |
| 12 Jun 2025 | Google began phasing out seven rarely used structured data types, including Course Info, Estimated Salary and Vehicle Listing; Google says the update does not affect ranking | Google Search Central blog | Keep markup that Google still documents, such as LocalBusiness, and check which of your types still produce a search feature |
| 28 Jun 2025 | The European Accessibility Act (Directive 2019/882) applies to e-commerce and other consumer services provided after this date | EUR-Lex | EU online sales and booking flows need accessible forms, checkout and content |
| 2 Sep 2026 | EN 301 549 V4.1.1 published with web requirements aligned to WCAG 2.2 Level A and AA; per law firm Davis Wright Tremaine, its legal effect starts after citation in the EU Official Journal | DWT, September 2026 | Build new sites to WCAG 2.2 AA now |
| 19 May 2026 | Google reported that AI Mode passed one billion monthly users and announced agentic booking for local services in the US | Google blog, I/O 2026 | Services, areas, hours and booking terms need to be stated in page text that a system can read |
Two more rules apply to many of our readers. In Ontario, businesses and non-profits with 50 or more employees have had to meet WCAG 2.0 Level AA on their public websites since 1 January 2021, per the Government of Ontario. Google's page experience documentation says Core Web Vitals are used by its ranking systems and that good scores alone do not guarantee top positions, so speed work goes together with content and pages.
Our conclusion for 2027: the competitor that wins is the one whose site answers the buyer's question in text, loads and reacts within the Google thresholds and lets anyone, including a person using a keyboard or screen reader, send a request.
How to measure the gap with your competitor
Put your site and the competitor's site side by side on the same seven rows and mark each row where you fall below the threshold. Everything in this table is visible from public pages and from Google's own reports.
| What to compare | Where you see it | You are behind when |
|---|---|---|
| Field speed: INP, LCP, CLS on mobile | PageSpeed Insights (Chrome field data) for both home pages and main service pages; Search Console Core Web Vitals report for your own site | Any of your metrics is outside "good" while the competitor's is inside |
| Pages per service and per area | The competitor's menu and sitemap.xml; a site: search on Google | They have a dedicated page for a service or area that you cover only in a shared list |
| Offer and proof on the first screen | Both sites opened on a 390-pixel phone screen | Your first screen lacks one of: the service, the area, a proof item (licence, founding year, Google rating, named clients), a call or request button |
| Request form | A test submission on both sites | Your form has more fields or steps, has no phone link, or gives no confirmation of what happens next |
| Structured data | Google's Rich Results Test and the Schema.org validator for both URLs | Your markup has errors, or the competitor describes the business, services and breadcrumbs and you do not |
| Accessibility | Keyboard-only pass through the menu and form; the accessibility score in PageSpeed Insights | Form fields lack labels, focus is invisible, or text fails contrast |
| Presence in AI answers | The same question about your service and city asked in Google AI Mode and ChatGPT | The competitor is named and you are absent |
The last row belongs to search as much as to the site. We cover it in detail in how to beat competitors in AI search (GEO) in 2027 and the ranking side in how to outrank competitors on Google in 2027.
A 90-day plan to build a site that wins
Fix speed and measurement first, then pages and the first screen, then markup, accessibility and the move to a new build if one is needed. Each step lists what to check and where we take it over.
Days 1–30: speed and measurement
- Find what slows interaction. Common causes of poor INP are long JavaScript tasks that run when a visitor taps: chat widgets, several tag managers, sliders, cookie banners loaded from third parties. List every script on the service page template and keep only those that bring requests or data you use.
- Load the main image and text first. LCP on service pages is usually the hero image or headline. Serve it in a modern format at the right size and avoid fonts and banners that move the layout after load, which raises CLS.
- Check that requests are counted. Each form submission and phone tap should be recorded once in analytics and in the ad accounts. This baseline is how you prove later that the new version brings more requests.
- Decide whether the current platform can reach the thresholds. If a builder template or an old WordPress theme keeps failing INP after the scripts are trimmed, we move the site to a fast static build: website rescue and migration.
Days 31–60: pages, first screen and forms
- One page for each service you sell. Each page states the service, who it is for, what is included, terms or price range if you publish them, and the proof that applies to that service.
- Area pages only where you work. Google's spam policies list "pages targeted at specific regions or cities that funnel users to one page" as doorway abuse. An area page needs local details: service radius, travel terms, local projects, the address or service area from your Google Business Profile.
- Offer and proof on the first screen. On a phone the first screen should show the service and area in the headline, one proof item and a request button. Long brand slogans push this content below the first screen.
- Shorter forms. Ask only for what you need for the first reply: name, phone or email, the service, an optional message. Add a visible phone link and a sentence about when you reply.
- Separate pages for paid traffic. A paid campaign should send visitors to a page built for one offer, with the same wording as the ad. We build them as landing pages for paid traffic; full sites and service catalogues go under corporate website development.
For the conversion side of these pages, see our website conversion guide for small business.
Days 61–90: structured data and accessibility
- Markup that matches visible text. Describe the organisation, each local business location, services, breadcrumbs and visible questions and answers. Google's LocalBusiness documentation lists address and name as required and hours, telephone, URL and geo coordinates as recommended. Types Google dropped in 2025 no longer produce a search feature, so keep them only where another system uses them. Validate every template, since one broken template repeats the error on every page built from it.
- Accessibility to WCAG 2.2 AA. Labels on every form field, visible keyboard focus, text contrast, alt text on meaningful images, captions on video. This covers AODA in Ontario (WCAG 2.0 AA) and the target of the new EN 301 549 for the EU.
- EU online sales. If you sell to consumers in the EU, check the checkout, booking and account pages against the EAA. The microenterprise exemption covers service providers with fewer than 10 staff and turnover or balance sheet up to €2 million, per Article 3 and Article 4(5) of the Directive.
- Technical audit after the changes. Crawl the site for broken links, redirect chains and duplicate titles; our technical SEO audit guide lists the checks.
Migration risks when the answer is a new site
A new site that beats the competitor on design can still lose traffic if old URLs break. Google's site move guide recommends permanent server-side redirects (301 or 308), keeping them at least one year and preferably indefinitely, and warns that visibility in Search may fluctuate for a few weeks or more on medium-sized sites.
- Redirect map before launch. Every old URL that has traffic or links gets a matching new URL, one to one. Sending everything to the home page loses the ranking of individual pages.
- Same content on matched pages. Texts, titles and headings that rank today move to the matching page in the first release; rewrites come after rankings settle.
- Tracking moves with the site. Analytics, ad conversion tags and Search Console verification are tested on the staging site before the switch.
- Watch two to four weeks. Compare Search Console clicks by page against the weeks before the move and fix 404 errors as they appear.
Why to hand this to a team under contract
- The cost of a mistake is traffic. A missed redirect map or a template with broken markup affects every page at once, and Google's own guide warns that rankings can fluctuate for weeks after a move.
- Speed, pages and markup depend on each other. A faster build that drops service pages loses rankings; new pages on a slow template fail INP. One team plans both.
- Scope in writing. We agree the page list, redirect map and acceptance thresholds (Core Web Vitals, validation without errors) in the contract before work starts.
- Experience across markets. Marketing MIX has built and moved sites since 2012, from 208 Booth Street in Ottawa, for clients in Canada, Ukraine, Germany and France. Our portfolio documents 126 projects.
The website is one part of the plan. For the full picture of where you compete, read a marketing strategy that beats your competitor in 2027 and the series overview what to bring into 2027: marketing, growth and investment.