Do I have to do anything when an update is released?

No. Updates are applied to your site by us, tested, and deployed. Your site stays live throughout and there is nothing for you to install, approve or pay for. You get an email telling you what changed and why it matters.

Does an update cost extra?

No. Every release on this page is included in the $225 a month. There is no upgrade fee and no separate SEO retainer. If we improve the standard, every client gets the improvement.

How often do updates come out?

Roughly every three to six weeks, plus smaller patches in between when something needs fixing. We release when the work is ready rather than to a calendar.

Will an update change how my website looks?

Usually not. Most releases are technical work behind the page: how search engines and AI assistants read your site, how fast it loads and how secure it is. When a release does change something visible, such as the enquiry form, it is called out in the release notes and it is done to get you more enquiries.

Do you tell Google when my site changes?

Yes. Since release 2.0.2 every client site is verified under our Search Console account, so when pages change the changed dates are updated and the sitemap is resubmitted to Google. That is what brings a crawler back to the page. Without it Google finds a change whenever it next happens to come by, which can take weeks.

What is AI search optimisation and why does it have its own releases?

A growing share of customers now ask ChatGPT, Google AI Overviews, Perplexity or Copilot for a recommendation instead of scrolling a results page. Those systems read your site with different crawlers and quote it in a different way, so being ranked on Google no longer means being recommended. Releases 1.4, 1.5 and 2.0 are the work that makes a site readable and quotable by those systems.

Website Updates: What We Ship to Every Client Site

2.2.2 17 September 2026 · 9:44am Enquiries

The touts stop at your form

Agencies send thousands of cold pitches a day through business contact forms, and a website form is the easiest door in. One arrived this week dressed as a new client enquiry, so it reached the inbox looking exactly like real work. Every Scalus form and every Scalus chat now reads what was written before it goes anywhere, and anything plainly selling marketing or search services is held. It never emails you and it never lands in your CRM.

Everything the form received today Quote for a retaining wall in Croydonto you I do SEO for local businesses, no cost for a lookheld Booking, Friday morning if you have itto you Are you interested in buying email leads?held

the touts stop before your inbox, and before your CRM

Held before your inbox, and before your CRM

The check runs on our side the moment the form is submitted, ahead of the email and ahead of the contact record. A pitch that is stopped leaves nothing behind: no notification, no contact to delete later, no name sitting in your database claiming it agreed to marketing.

It reads the shape of a pitch, not a list of banned words

The one that got through this week was written like a person, with none of the usual spam phrases in it. What every pitch does have is two things at once: the thing being sold, and the giveaway that it is being sold at you, whether that is having looked your site up, a problem they invented for you, an offer to fix it, or a marketing job title in the sign off.

A real customer who happens to sell marketing still gets through

Someone writing that they do SEO as a sole trader and need a bookkeeper is a real job, not a pitch, so describing your own business is never enough on its own to be held. The rule is deliberately set to let a tout through rather than risk losing one real enquiry.

The website chat is covered too

The chat quietly creates a contact record from the first message, so a pitch typed in there was reaching the CRM without ever touching the form. It now runs the same check, and anyone with a genuine question is unaffected.

A check that runs before anything goes live

Every form and chat across the fleet is now audited automatically, which proves the protection is in place on each one and running the current rules, rather than assumed. A site cannot go live without it.

Applied to Every live Scalus client site, both the enquiry form and the website chat. Nothing was required from you.

2.2.1 13 September 2026 · 2:08pm Platform

One credit on every site, and all of it clickable

Every Scalus site carries a small line in the footer saying who built it. Across the fleet that line had drifted into eleven different versions, and on several sites only the last word was a link. It is now one mark on every site, with the Scalus logo beside the words, the whole block clickable, and the colour chosen to stay readable on whatever that footer is painted.

One credit, readable on a dark footer and a light one

The whole line is the link now

On five sites only the word Scalus was clickable, so anyone aiming at the words either side of it hit nothing at all. The logo and the words are now a single link, which is a much easier target on a phone.

The logo is there, and it stays crisp

The Scalus mark sits beside the words rather than the words standing alone. It is drawn rather than loaded as an image, so it is sharp on any screen, costs no extra load on the page, and cannot break if a file path ever changes.

Readable on a dark footer and a light one

Black on light, white on dark. Rather than guessing, every footer on the fleet was photographed as a visitor sees it and the brightness measured, then the colour chosen from that number. Twenty sites came out dark, one light, and every one of them clears the accessibility standard for contrast with room to spare.

It cannot quietly go missing again

Seven sites build their pages from a template, so a credit fixed on the page alone would come back wrong the next time that site was rebuilt. The templates were fixed too, the mark now carries its own styling so nothing can strip it, and a check that loads all twenty one live sites and measures the result now runs as part of going live.

Applied to Every live Scalus client site, and the check that runs before anything goes live. Nothing was required from you.

2.2 11 September 2026 · 7:45am Platform

Every site checked on the iPhone Duo

The iPhone Duo, Apple's folding phone, puts two screen sizes on the map that no phone had before: one when it is shut and a much wider one when it opens. Every Scalus client site was loaded at both, measured rather than eyeballed, and the checks that run before anything goes live now cover them permanently.

466px folded

626px open

the menu stays pinned to the edge as the screen opens

Two new screen widths, both measured

Shut, the iPhone Duo is wider than any phone we had ever designed for. Open, it is wider again, closer to a small tablet than a phone. Every live site was loaded at both sizes and the header, the layout and the sideways scroll were measured on the rendered page.

The menu button that would have been cut in half

One site had a menu button running past the right edge of the open screen, sliced in half and impossible to tap. It passed every check we had, because every check we had stopped at the width of an ordinary phone. It was found, fixed and live the same morning.

The rest held up, and that is the finding

Nothing scrolled sideways, no image broke and no layout collapsed on any other site at either width. Sites built to bend rather than to a fixed size handle a screen that did not exist when they were built, which is the entire argument for building them that way.

The new widths are now part of the gate

The review that runs before and after every change now measures five widths instead of two, so the iPhone Duo is covered on every site from here on without anyone having to remember it.

A measuring fault found and fixed on the way

Two more sites looked like they had the same problem and did not. The checker was reading the text inside a button instead of the button itself, which made a correctly placed button look off centre. The checker was corrected and both sites were left exactly as they were.

Applied to Every live Scalus client site, and the pre publication check that runs on all of them. Nothing was required from you.

2.1.3 10 September 2026 · 5:49pm Enquiries

One enquiry, one record, even with a slow upload

A form carrying several photos could run out of time on the server, tell the sender to try again, and file the same enquiry more than once. Every form now has six times the headroom, the slow steps run side by side, and a repeat send updates the record it already made.

Enquiry sent six photos, 4MB

7s

One job card filed once, updated on a repeat

a slow upload now finishes, and a repeat send updates the same record

Six times the headroom

Each enquiry used to have ten seconds to reach the CRM, the job system and the inbox. One photo could use eight of them. Every Scalus site now allows a full minute, so a slow connection or a large upload finishes instead of failing.

The slow steps run side by side

Filing the job card and sending the notification used to wait on each other. They now run at the same time, and photos upload together rather than one after another, so a six photo enquiry finishes in about seven seconds.

A repeat send updates, it does not duplicate

If someone sends the same enquiry twice within a few hours, the job system now finds the record it already made and updates it with the latest details and photos, instead of filing a second card next to the first.

Proven with real photos, not an empty test

The fix was checked with a test enquiry carrying six photos at the largest size the form allows, the worst case a customer can send, and with every live site probed after the change. No enquiry reached any business while this was checked.

Applied to Every live Scalus site with an enquiry form, and the repeat send update wherever a site files job cards. Nothing was required from you.

2.1.2 9 September 2026 · 4:20pm Enquiries

Every enquiry form now confirms it sent

Every form on every Scalus site now ends the same way. The fields fade out and a confirmation fades in where they stood, with a green tick that draws itself, so nobody is left wondering whether their message went through.

Thank you for your enquiry Message sent

the confirmation, in the form's own box

The confirmation happens inside the form

The form does not vanish and the page does not jump. The fields fade out and the message fades in inside the same panel, keeping the same border and the same corners, then the panel eases down to the height the message needs.

A green tick that draws itself

The circle draws, then the tick, then the words. Something completing on screen reads as a send that worked, where a line of text simply appearing does not, and that is the moment people decide whether to send again or walk away.

It takes on the design of the site it is on

The confirmation reads its own page and uses that site's background, corners, heading face and text colour. It looks like part of the site rather than a widget dropped on top, on a dark studio site and a cream wellness site alike.

Nothing useful is lost in the swap

Where a confirmation already carried something worth keeping, a booking link, a phone number for urgent jobs or a summary of the answers given, that now sits under the message instead of disappearing with the form.

Checked on a phone and a desktop, site by site

Every live site was loaded at phone and desktop width and put through a real send with the lead going nowhere, so the confirmation was measured on the page rather than assumed. No enquiry was sent to any business while this was checked.

Applied to Every live Scalus site with an enquiry, quote, booking or intake form. Nothing was required from you.

2.1.1 20 August 2026 · 2:42pm Enquiries

Quote forms rebuilt as three short steps

The enquiry form on every site was rebuilt as three short steps with a progress bar, so people finish it instead of abandoning a long single page form.

Mobile number0468 085 444

56pxtouch target

step 1 of 3

Three steps instead of one long form

A form that shows every field at once reads as work, and people leave. The same questions split across three short steps with a progress bar in view show visible progress, so far more enquiries get finished and sent.

Floating labels and 56 pixel touch targets

Each field label now starts inside the field and lifts above it once you start typing. That frees the vertical space to make every field 56 pixels tall, which is the size a thumb hits reliably on a phone without zooming.

Photo upload on quote requests

Customers can attach photos of the job with the enquiry. You get to quote from what you can see rather than from a description, which cuts the back and forth before a job is booked.

How did you hear about us

An optional question added to quote forms so you can see which channel is producing work, rather than guessing.

Applied to Every live Scalus site with a quote or enquiry form. Nothing was required from you.

2.1 15 August 2026 · 12:15pm Search

Pages stopped competing with each other

A full audit of every site to find pages that were chasing the same Google search as each other, plus a check of how many pages Google has indexed rather than merely crawled.

page oneElectrician Melbourne East

page twoSwitchboard upgrades Ringwood

one page, one search

One page, one search term

When two pages on the same site target the same search, Google picks one and quietly suppresses the other, so they hold each other down. Every page title across the fleet was checked for a term no other page carries, and overlapping pages were re angled onto their own search.

Published is not the same as indexed

A page can be live, crawled by Google, and still never enter the index. The number of pages Google has indexed is now compared against the number in the sitemap on every site, and the gap gets investigated rather than assumed away.

Thin pages found and filled

A page Google crawls and finds nothing distinctive on gets dropped. Pages carrying under roughly 150 words of genuine content were flagged and rewritten to say something the other pages do not.

The checker learned to crawl

Our own site checker could only ever grade one page at a time, so it was structurally blind to problems that exist between pages. It now crawls the whole site and reports on the relationships as well as the pages.

Applied to All 14 live sites audited. Nothing was required from you.

2.0.2 10 August 2026 · 6:10pm Search

Search Console under one roof

Every client site was brought under a single verified Search Console account, so new pages can be submitted to Google automatically instead of waiting to be found.

sitemap received

search console

Verified ownership on every property

A Scalus service account was added as a verified owner of every client property in Google Search Console. That is the permission that lets sitemaps be submitted and indexing be requested through the API rather than by hand.

Automatic resubmission after every change

When a page changes, Google no longer has to stumble across it. The changed date on that page is updated and the sitemap is resubmitted to Google as part of the deploy, which is the signal that brings a crawler back to the page rather than leaving it until one happens to pass.

Spam blocked at the form

Automated submissions selling web design and SEO services were reaching client inboxes through the enquiry forms. Those are now filtered at the point the form is received, so what lands in your inbox is a real enquiry.

Applied to Nine sites verified, spam filtering on every lead form. Nothing was required from you.

2.0.1 5 August 2026 · 8:55pm Security

One address, clean code, locked down headers

Every site now answers on exactly one address, its code passes validation with no errors, and browsers are told to treat it as a secure page.

yoursite.com.au www.yoursite.com.au

one address, all of the strength

canonical

One canonical home

A site reachable at both the plain domain and the www version looks like two competing copies to Google, splitting whatever ranking strength it has earned. Each site now redirects permanently to one of the two, so all of that strength lands in one place.

Validation errors cleared

Every page was run through the W3C validator and the remaining markup errors were fixed. Broken markup is where search engines lose track of the structure of a page, and it is the cheapest class of problem to have and to fix.

Security headers

Sites now send the standard protective headers on every response, which stop the page being embedded inside another site, stop the browser guessing at file types, and force the secure connection. It is invisible to visitors and it is one of the things a technical audit looks for.

Answer blocks on the homepage

The frequently asked questions block and its structured data were extended onto homepages, not just the FAQ page, because the homepage is the page an AI assistant is most likely to read first.

Applied to Every live Scalus site. Nothing was required from you.

2.0 29 July 2026 · 8:54pm AI search

The AI search release

The largest release so far. Every site was rebuilt to be readable and quotable by AI assistants, which is now where a growing share of customers ask for a recommendation before they ever open Google.

GPTBotClaudeBot PerplexityBotGoogle Extended ApplebotOAI SearchBot BingbotAmazonbot and 13 more

21 agents welcomed

Question and answer structured data across every site

Questions and answers were added throughout each site and marked up in the format search engines and AI models read. This is the single strongest signal for getting quoted by an AI assistant, because the model is looking for a clear question with a direct answer under it rather than a paragraph it has to interpret.

The full 2026 AI crawler set, 21 agents

Most websites silently block the crawlers behind ChatGPT, Claude, Perplexity, Google AI Overviews, Copilot and Apple Intelligence, usually without knowing it. Every Scalus site now explicitly welcomes all 21 of them by name, which is the precondition for being cited at all.

Answers written to be quoted

Every answer now leads with the direct answer before any context. An AI model quotes the first clear sentence that answers the question, so burying the answer under an introduction is the most common reason a page is read and never cited.

Heading order and screen reader labels

Heading levels were put back into a real order and the accessibility labels were corrected across every page. Both machines reading your site and people using a screen reader rely on that structure to work out what the page is about.

Applied to Every live Scalus site. Nothing was required from you.

1.5.1 27 July 2026 · 7:35pm Search

Real link previews and image search

When your page gets shared in a text message, on Facebook or in an email, the preview card now shows a real screenshot of that exact page instead of a generic logo.

link preview

A screenshot of every page, not one image for the site

Over 40 pages per site were screenshotted at share card size, so the preview shows the page being shared rather than a stand in. A link with a real preview gets clicked noticeably more often than a bare link.

Image files renamed to describe themselves

Image files named after the camera or the export tool tell Google nothing. Every image was renamed to describe what it shows, which is how a photo of your own work starts appearing in Google Images for the service it depicts.

Preview images compressed

The preview screenshots came to 45 megabytes and were reduced to 3.3 megabytes with no visible loss, so the gain in sharing did not cost anything in page speed.

Site search that search engines can see

A working search page was added and declared in the structured data. That is what allows Google to show a search box under your listing and lets it index the pages a search would surface.

Applied to 11 sites, over 200 preview images. Nothing was required from you.

1.5 22 July 2026 · 6:10pm AI search

The entity graph

Each site now describes itself to search engines as a connected set of facts about one business, rather than as a stack of unrelated pages.

one business, every page

Every page carries the business identity

The business, its address, its service area, its hours and its contact details are attached to every page under one stable identifier, and each page type points back at that identifier instead of repeating it. Google and the AI models are then reading one business with many pages rather than many pages that happen to share a name.

Breadcrumb trails on every sub page

Each page declares where it sits in the site. That is what produces the readable trail under a Google result instead of a raw address, and it is how a search engine understands which pages are the important ones.

Page types declared

Contact pages, about pages, service pages, listings, courses and articles are each declared as what they are. A search engine that knows a page is a service page in a suburb can match it to a search for that service in that suburb.

A plain text summary for AI models

Each site gained an llms.txt file, which is a plain summary of the business, the areas it serves, its ratings and its most common questions, written for AI models to read directly. It is emerging as the standard way to hand an AI assistant the facts rather than hoping it infers them.

Applied to Every live Scalus site. Nothing was required from you.

1.4.1 14 July 2026 · 6:07pm Search

Sitemaps that keep themselves current

The sitemap on sites with a blog or news section now builds itself, so a new article is announced to Google the moment it is published.

/services/18 Aug

/areas/ringwood/19 Aug

/news/todays postadded on its own

sitemap.xml

The sitemap generates on request

A sitemap is the list of pages a site hands to Google. Hand maintained, it goes stale the first time anyone forgets it. It is now generated live from the pages that exist, so it cannot fall behind.

Every article included automatically

New posts are added to the list as they publish, with an accurate last modified date, which is the signal Google uses to decide how often to come back and look.

Applied to Sites with a blog, news or journal section. Nothing was required from you.

1.4 2 July 2026 · 6:24pm Search

Every page indexable, every page canonical

The release that turned the search work into a standard applied identically to every site rather than something done page by page.

/services/ blockedindexable

/areas/ blockedindexable

/contact/ blockedindexable

let into the index

Every page allowed into the index

Pages were audited for accidental blocking. A single stray instruction left over from a staging site keeps a page out of Google entirely, and it is invisible unless you go looking for it.

One official address per page

Every page declares its own official address. Without it, a page reachable by more than one route can be treated as duplicate content and have its ranking strength divided.

Titles and descriptions written per page

Each page got its own title and description written for the search someone would type, rather than the business name repeated 30 times.

AI crawlers welcomed for the first time

The robots file, which tells automated visitors what they may read, was rewritten to explicitly welcome the AI crawlers rather than leave them to guess. This was the first version of what became release 4.0.

Applied to Every live Scalus site. Nothing was required from you.

1.3.1 25 June 2026 · 7:35am Search

Structured data and Search Console

Sites started describing their own facts in the format Google reads, and every site was connected to Google Search Console so its real performance could be seen.

address, hours, area served

The business described in machine readable form

Name, address, service area, opening hours, price range and social profiles were added as structured data. This is what Google reads when deciding whether to show a business in the local map results for a nearby search.

Verified in Google Search Console

Every site was verified with Google, which is the only place the real numbers live: what people searched to find you, which pages they landed on, and which pages Google has refused to index.

Area pages

Sites serving multiple suburbs gained pages targeted at those suburbs, so a search naming a suburb has a page to match rather than a homepage that mentions ten of them.

Applied to Every live Scalus site. Nothing was required from you.

1.3 13 June 2026 · 4:51pm Search

Search foundations

The start of the search standard. Sitemap, crawler instructions and proper page metadata became a required part of every site rather than an optional extra.

→

one page ranks for one thing

Sitemap and crawler instructions on every site

A sitemap listing every page and a robots file telling crawlers what they may read became standard on every build. Without them a search engine finds your pages by chance.

Real page metadata

Titles, descriptions and the tags controlling how a page appears when shared were written for every page rather than inherited from a template.

Multiple pages instead of one long page

Sites were expanded so each service, each area and each purpose has its own page. One page can rank for one thing, so a single page site is competing for one search no matter how good it is.

Applied to Every site built from this point forward. Nothing was required from you.

1.2.1 14 May 2026 Platform

Tracking and attribution

Enquiries started carrying the story of where they came from, so ad spend could be judged against jobs won rather than against clicks.

browser

blocked

our server

recorded

same event, counted once

Conversion tracking on every form

A completed enquiry is now recorded as a conversion rather than treated as an ordinary page view, which is the event ad platforms need in order to find more people like the ones who enquire.

Server side tracking as well as browser side

Browser tracking is blocked for a large share of visitors by ad blockers and privacy settings. The same event is now also sent from our server, sharing one identifier so it is never double counted, which recovers the enquiries that were previously going unrecorded.

Campaign details carried into the enquiry

The campaign and ad that produced a visit travel with the form submission, so an enquiry can be traced back to the specific ad that created it.

Applied to Client sites running paid campaigns. Nothing was required from you.

1.2 16 April 2026 Performance

Hosting and speed

Sites moved onto hand written code served from the edge, replacing page builder templates, and started loading in under a second.

time to first paint

0.7s

served from the edge

Served from the edge

Pages are delivered from the network location closest to the visitor, with the certificate handled automatically, so a page in Melbourne is served from Melbourne. Loading speed is a confirmed Google ranking factor and it is also the first thing a visitor judges you on.

No page builder, no theme

Sites are hand written rather than assembled in a page builder. A page builder ships the code for every feature it might need, which is why those sites are slow, and there is no way to fix that from inside the builder.

Instant rollback

Every deploy is kept, so a change can be reversed in seconds if something is wrong. Nothing that goes live is ever a one way door.

Applied to Every client site. Nothing was required from you.

1.1 19 March 2026 Enquiries

Instant response on every enquiry

The moment someone enquires, they get an acknowledgement and you get a notification, because the first business to reply usually wins the job.

Thanks for getting in touch, I have your details and will call you shortly.

8safter enquiry

automatic reply

Automatic text message within seconds

An enquiry triggers an immediate SMS to the customer, so they know they reached a real business and are not left wondering. The response gap is where most enquiries are lost to whoever answered first.

Notification straight to your phone

You are notified as it arrives, with the enquiry details, rather than finding it in an email inbox later that night.

Applied to Every client system. Nothing was required from you.

1.0.2 27 February 2026 Platform

Client dashboards

Each client got a private dashboard showing their enquiries and results as they happen, rather than a report at the end of the month.

enquiries by month

Your own dashboard address

A private dashboard on its own address showing enquiries, where they came from and what they are worth, updated as things happen.

Built to look like your site

The dashboard carries your brand rather than ours, so it reads as part of your business.

Applied to Every client. Nothing was required from you.

1.0.1 6 February 2026 Enquiries

Lead capture and pipeline

Enquiries stopped being emails to be remembered and became records in a system that tracks them through to a job.

NameMobile

→

Contact created, stage set, nothing sitting in an inbox

every enquiry tracked

Name and mobile, nothing more

Every field added to a form costs completions. Forms were cut back to a name and a mobile, with any qualifying detail asked afterwards rather than upfront.

Every enquiry recorded and tracked

Enquiries land in a system that holds the contact, the history and the stage they are at, so nothing sits unanswered in an inbox.

Applied to Every client system. Nothing was required from you.

1.0 15 January 2026 Platform

Platform foundation

The base every Scalus site has been built on since: managed hosting, secure connections, and one system maintained across every client rather than a separate build for each.

one build

improved once, applied to all

One platform, maintained centrally

Client sites run on one maintained system. That is what makes a release like this one possible at all: an improvement is built once and applied to everybody, instead of being quoted as a separate job per site.

Secure by default

Certificates, renewals and secure connections are handled automatically, so a site can never quietly lapse into the browser warning that costs you visitors.

Applied to Every client site. Nothing was required from you.

Your website is never finished

The touts stop at your form

Release history

The touts stop at your form

Held before your inbox, and before your CRM

It reads the shape of a pitch, not a list of banned words

A real customer who happens to sell marketing still gets through

The website chat is covered too

A check that runs before anything goes live

One credit on every site, and all of it clickable

The whole line is the link now

The logo is there, and it stays crisp

Readable on a dark footer and a light one

It cannot quietly go missing again

Every site checked on the iPhone Duo

Two new screen widths, both measured

The menu button that would have been cut in half

The rest held up, and that is the finding

The new widths are now part of the gate

A measuring fault found and fixed on the way

One enquiry, one record, even with a slow upload

Six times the headroom

The slow steps run side by side

A repeat send updates, it does not duplicate

Proven with real photos, not an empty test

Every enquiry form now confirms it sent

The confirmation happens inside the form

A green tick that draws itself

It takes on the design of the site it is on

Nothing useful is lost in the swap

Checked on a phone and a desktop, site by site

Quote forms rebuilt as three short steps

Three steps instead of one long form

Floating labels and 56 pixel touch targets

Photo upload on quote requests

How did you hear about us

Pages stopped competing with each other

One page, one search term

Published is not the same as indexed

Thin pages found and filled

The checker learned to crawl

Search Console under one roof

Verified ownership on every property

Automatic resubmission after every change

Spam blocked at the form

One address, clean code, locked down headers

One canonical home

Validation errors cleared

Security headers

Answer blocks on the homepage

The AI search release

Question and answer structured data across every site

The full 2026 AI crawler set, 21 agents

Answers written to be quoted

Heading order and screen reader labels

Real link previews and image search

A screenshot of every page, not one image for the site

Image files renamed to describe themselves

Preview images compressed

Site search that search engines can see

The entity graph

Every page carries the business identity

Breadcrumb trails on every sub page

Page types declared

A plain text summary for AI models

Sitemaps that keep themselves current

The sitemap generates on request

Every article included automatically

Every page indexable, every page canonical

Every page allowed into the index

One official address per page

Titles and descriptions written per page

AI crawlers welcomed for the first time

Structured data and Search Console

The business described in machine readable form

Verified in Google Search Console

Area pages

Search foundations

Sitemap and crawler instructions on every site

Real page metadata