Structured data

It is what turns a string into a thing: this is an organisation, with this licence number, at this address; this is an offer, at this price, in this currency. Search engines use it for result features, and assistants use it to resolve which entity a page is about — which is the more durable of the two benefits.

Identity is the part worth getting right. Give the organisation one stable @id and reference it from every other node on the site rather than repeating the name. That is the difference between a search engine seeing forty pages that mention a company and seeing forty pages published by one.

Marking up a claim the page does not make

Structured data that disagrees with the visible page is the one reliable way to have it ignored, and repeated often enough it costs the site its eligibility for result features entirely. Generate the markup from the same data the page renders, so the two cannot drift.

GEO

Being citable by an assistant that is assembling an answer, rather than merely rankable by an engine that is returning links.

---

SEO

Making a site findable by search engines for the questions its buyers actually ask — a structural property of the site far more than a list of tasks performed on it.

---

Canonical URL

The one address a piece of content declares as its real one, so that every variant of it consolidates into a single entry rather than competing with itself.

All forty-five termsWhat this is regulated by in the UAE

Is this one right in your own numbers?

The definitions are the easy part. Whether the figure on your dashboard was computed this way is a different question, and usually the more expensive one.