For your AI and the curious
SEO: head tags, schema and files
SiteShip writes the head tags, schema.org data, sitemap, robots.txt, feed and llms.txt. You set frontmatter and data/site.yaml.
On this page
SiteShip writes the whole <head> on every page: title, description, canonical link, robots, Open Graph and Twitter tags, and schema.org JSON-LD. It also serves the sitemap, robots.txt, the feed and llms.txt. You set the data in frontmatter and data/site.yaml. You never write the tags.
This page covers the seo and local-seo topics of the connector's guide tool. The owner's version is Get found on Google.
Frontmatter
Every page should have these three fields:
---
title: How to Choose a Wedding Photographer
description: A practical guide to finding the right photographer for your wedding day. Questions to ask, what to look for, and how to compare packages.
image: /assets/images/wedding-guide.jpg
---
| Field | Notes |
|---|---|
title |
What the page is, with the words people search for first. No site name. |
description |
120 to 160 characters, written for a person reading a search result. |
image |
The image shown when the page is shared. Ideally 1200×630 pixels. Falls back to defaultImage in data/site.yaml. |
Site-wide values are in data/site.yaml:
name: Acme Photography
description: Austin wedding and portrait photographer
defaultImage: /assets/images/share.jpg
A page generated from data takes its title, description and share image from each item: title or name, description or summary, and image. Give every item a summary and an image so each page has its own. See Data files and generated pages.
Every image needs a descriptive alt. SiteShip adds loading="lazy", but not alt. A missing one is reported (author.image_missing_alt).
The title rule
- The tab title is "Page title | Site name".
- The home page, with no title or
title: Home, is the site name alone. Give it a real title to rank for more:title: Family Dentist in Mount Pleasant, SC. - A title that already contains the site name is not given it twice.
- The
checktool flags a title over 60 characters. It counts the whole tab title, with the " | Site name" suffix. For a site named "Harbor Dental", that suffix is 16 characters, so keeptitle:to 44.
What check reports for each page, in its seo_issues list:
| Rule | Reported when |
|---|---|
title_missing, title_long |
No title, or the tab title is over 60 characters |
description_missing, description_long, description_short |
No description, over 160 characters, or under 50 |
title_duplicate, description_duplicate |
Two or more pages share one |
h1_missing |
The page has no <h1> |
orphan |
No other page links to it |
og_image_missing |
No share image. One defaultImage fixes every page |
These never block a publish. A page with robots: noindex is skipped.
Schema written for you
| Data present | Schema |
|---|---|
| Every page | Organization and WebPage |
| Every page except the home page | BreadcrumbList |
A Markdown post with date |
Article. date becomes datePublished |
address in data/site.yaml |
LocalBusiness on the home page |
type: faq in a page's frontmatter, plus data/faq.json |
FAQPage on that page |
Never write schema.org JSON-LD by hand. A hand-written copy is reported (author.hand_written_schema). Add the data to frontmatter and data/site.yaml instead.
SiteShip writes no star-rating schema from the site's own reviews.
To see what a page carries, call preview on it. The answer includes the page's schema.org markup.
Local business fields
With address set, the home page gets LocalBusiness (or the businessType you name) with name, address, phone, email, opening hours, logo and priceRange, plus GeoCoordinates from lat and lng, and areaServed from serviceArea.
name: Acme Plumbing
type: business
businessType: Plumber
phone: "(512) 555-0100"
email: hello@acmeplumbing.com
address:
street: 123 Main St
city: Austin
state: TX
zip: "78701"
lat: 30.2672
lng: -97.7431
hours: "Mon-Fri 7am-6pm; Sat 8am-12pm; Sun closed"
serviceArea: [Austin, Round Rock, Cedar Park, Georgetown]
Quote phone and zip. As numbers they lose leading zeros and are refused.
hours
hours is one string. The site shows it as written, and SiteShip turns it into schema.org opening hours. Write days, then times, with parts separated by ;.
| Written | Read as |
|---|---|
Mon-Fri 8am-5pm; Sat 9am-1pm; Sun closed |
Mo-Fr 08:00-17:00, Sa 09:00-13:00 |
Monday to Friday 9:00am - 5:30pm |
Mo-Fr 09:00-17:30 |
Mon, Wed, Fri 9am-5pm |
Mo,We,Fr 09:00-17:00 |
Tue-Sat 11am-2pm, 5pm-10pm |
Two ranges a day |
Sun 10am-2pm (brunch) |
Su 10:00-14:00. A note in brackets is shown, not read |
Weekdays 9am-5pm, Daily 10am-10pm |
Mo-Fr, Mo-Su |
Mon-Fri 08:00-17:00 |
24-hour times |
24/7, Open 24 hours |
Mo-Su 00:00-24:00 |
A part with closed is skipped. A part with words in place of times, such as Sat by appointment, is not read. If any part can't be read, the schema gets no hours at all and the write reports author.hours_unreadable. Put a short note in brackets after the times, or a longer one in its own field, such as hoursNote, printed beside {{ site.hours }}.
businessType
businessType is the schema.org LocalBusiness subtype, written as schema.org writes it: one word, capital first letter, letters only.
businessType: HairSalon # valid
# businessType: Hair Salon # not valid
Others: Dentist, Plumber, Electrician, Restaurant, LegalService, RealEstateAgent, AutoRepair, HVACBusiness. SiteShip checks the form, not schema.org's list, so use a real type name.
Left out, the type comes from the site type:
Site type |
Schema type |
|---|---|
health |
MedicalBusiness |
restaurant |
Restaurant |
beauty |
HealthAndBeautyBusiness |
fitness |
ExerciseGym |
real-estate |
RealEstateAgent |
hospitality |
LodgingBusiness |
| Anything else | LocalBusiness |
A site whose type is blog, portfolio, saas or landing-page gets no LocalBusiness schema unless businessType is set. type stays one of SiteShip's site types; a value outside them is refused (author.site_type_invalid).
Reviews
Reviews are a list in data/reviews.json with author, rating (a number from 1 to 5), text and date (YYYY-MM-DD). Only real reviews the owner supplies, word for word. The page can show them and their average. The engine does not turn them into star-rating markup.
sitemap, robots, feed, llms.txt
SiteShip serves these. They are never files in the site.
| Address | What it is | How to influence it |
|---|---|---|
/sitemap.xml |
Every public page, generated pages included | robots: noindex leaves a page out. modified or a post's date becomes <lastmod> |
/robots.txt |
Allows all crawlers and links to the sitemap | Not configurable |
/feed.xml |
RSS feed of blog posts | A post needs date to appear |
/llms.txt |
What the site is and its pages, in Markdown, for AI assistants | The same pages as the sitemap |
/search, /search.json |
Site search over titles, descriptions, keywords and page text |
search: false leaves a page out |
All of them read one list of public pages. Left out everywhere: the 404 page, a page with robots: noindex, a page with draft: true, and a page with a future publishDate.
To tell Google about the sitemap, submit https://yourdomain.com/sitemap.xml in Google Search Console. A verification <meta> tag goes in templates/components/head.html.
robots
---
title: Thank You
robots: noindex
---
robots sets the page's robots meta tag. Common pages to noindex are /thanks and /success. A noindex page is left out of the sitemap, the feed, llms.txt and site search.
/robots.txt itself is not configurable.
Tags you never write
A <title>, meta tag, canonical link, Open Graph or Twitter tag written by hand is dropped, and reported:
| Where it was written | Code |
|---|---|
A layout or head.html |
author.engine_head_tag |
| A page | author.head_tags_outside_head |
Related pages
Something wrong on this page? Email support@siteship.ai. Checked on November 14, 2026.