Terms we actually use on a website project.

The address you declare as the one true copy of a page when duplicates exist.

Search engines often see the same content at www and non-www, with and without a trailing slash, or on a print view. A rel=canonical tag points them at the URL you want indexed. Each locale on this studio site canonicalizes to itself, not to English.

A rebuild that launches without deciding canonicals lets Google pick. It often picks the weaker copy.

Annotations that tell search engines which language and market a URL is for, and which URLs are its siblings.

Every language version should list itself and the others, plus x-default for the fallback. The signal has to be reciprocal. Turkish pointing at English while English ignores Turkish is an incomplete handshake.

Hreflang does not translate the page. Native copy still has to answer the query people type in that market. See the multilingual SEO article.

A machine list of canonical URLs you want crawled, with last-modified dates and language alternates when the site is multilingual.

A sitemap is not a ranking boost. It is a map. If lastmod is always 'today,' crawlers learn to ignore it. This site writes real dates and xhtml alternates between locales.

Submitting the sitemap in Search Console still matters. The file existing in /sitemap.xml is not the same as Google fetching it on a schedule you control.

The indexable structure of a public site: titles, headings, crawlable links, canonicals, hreflang, sitemap, robots, redirects.

We include this in website delivery. It is not a promise that a keyword will sit in position one. Quality gates check that important URLs have a subject and that old addresses are mapped on a rebuild.

Content, links from other sites, and local reputation sit outside this definition. Those are not 'technical' and we do not sell them as a ranking package.

An interface designed and built for the brand, not a marketplace theme with new colors.

Custom still uses templates inside the project: a shared article layout, a repeated product module. The difference is ownership of those patterns and of the code at handoff.

METEK does not resell ready-made themes as custom work. If you need a content panel, we build the fields the team will use.

Internal screens whose objects match the business: lines, rooms, leads, articles, not a generic CRM's contacts and deals unless that is the job.

A panel is software. A website is the public face. They can ship together when the team must update the public site or process inquiries without a developer.

Off-the-shelf CRM is the right buy when your objects already match the product. Custom wins when Friday still means exporting a spreadsheet. The comparison article spells out the fork.

Structured data in JSON-LD that names the organization, pages, articles, FAQs, and services in a vocabulary machines share.

Useful schema restates facts already visible on the page. Fake review stars, invented aggregate ratings, and Organization markup that claims offices you do not have are how you earn a manual action.

This site marks ProfessionalService, Person, WebSite, FAQPage, Service, BlogPosting, BreadcrumbList, and on this URL a DefinedTermSet. See the schema article for what belongs on a client site.

A written list of old URLs to new URLs used before a rebuild goes live, usually as 301 redirects.

Search engines have already stored your service pages, blog posts, and product URLs. Changing the path without a map hands that history to a 404.

The map is a delivery line on a redesign, not a favor after launch. The redesign article covers the rest of the checklist.

Pages and listings whose subject is a service in a place people actually search, kept consistent with the business profile.

A homepage that says 'we serve the whole region' is not local SEO. Service pages and honest area pages are. Google Business Profile is a sibling surface, not a replacement for those URLs.

We do not guarantee Map Pack rank. We build the page set and keep name, address, and phone aligned. The local services industry page and article describe the architecture.

The title is the clickable headline in search results. The description is the supporting sentence. Both should match the page subject.

One subject per URL. Stuffing every service into one title teaches the engine nothing. Descriptions are written as sentences, not keyword lists.

On a multilingual site the title is drafted in the market language. Translating the English title word for word is how four locales compete with each other.

Whether search engines store a URL and may show it. Controlled by robots, noindex, canonicals, and whether the URL is linked and listed in the sitemap.

Staging sites, thank-you pages, and filter combinations often should stay out of the index. Public service pages should be in. Mixing those flags is a common launch defect we check before handoff.

Indexation is not ranking. A stored page can still sit on page four. The technical checklist article lists the flags we review.

Generative engine optimization: making the studio easy to cite accurately in AI answers, starting with a plain llms.txt at the site root.

AI crawlers read the same public HTML as Google. They also look for a short, quotable statement of who you are, what you build, and what you will not claim. This site publishes /llms.txt and /llms-full.txt with those limits: no invented awards, rankings, or fixed prices.

GEO does not replace titles and pages. If the underlying site is a thin theme, a text file will not save the citation. The FAQ and service landers are the pages we expect models to quote.