Page SEO settings

Page Settings controls how each page is described to search engines and social networks. ArtInStack also adds structured data (JSON-LD) on several public URLs and image licensing metadata on photo detail pages—those are separate from the fields in this tab but matter for discovery and Google Image Search.

Set page-level SEO under Pages → Edit → Page Settings. For portfolio-wide photo indexing and map visibility, see Portfolio geo visibility and impact maps and Photo detail pages.

What you control on each page (Page Settings → SEO card)

Field	What it does on your live site
Meta title	Browser tab title and primary search headline (<title>). Falls back to page title + site name if empty.
Meta description	Summary in search snippets (<meta name="description">).
Canonical URL	Optional override for the canonical link tag (advanced—leave blank unless you use a separate canonical domain strategy).
OG image	Image used when the page is shared on social networks (Open Graph).
Hide from search engines	Adds noindex / nofollow robots meta so crawlers should not index this page; page is also omitted from your site sitemap.xml.

The editor shows character hints (~60 for title, ~160 for description). Save Page after changes, then Publish if the page should be public.

Page title (in Page Details) is your dashboard label; Meta title is what search and social systems prefer for the public URL.

What ArtInStack adds automatically (beyond Page Settings)

These ship on your published photographer site (subdomain or custom domain). You do not paste JSON-LD by hand.

Standard pages (home + editor-built pages)

Signal	Where it appears
HTML meta tags	<title>, description, canonical URL, Open Graph image (when set), robots when hidden
BreadcrumbList JSON-LD	In-page <script type="application/ld+json"> on each public page
Organization JSON-LD	On your homepage only (site name + URL)
Sitemap	https://yoursite.example/sitemap.xml lists published pages; includes image entries when a page has an OG image

Interior pages do not currently emit a full WebPage schema block—breadcrumbs + meta tags are the main page-level signals.

Blog posts

Blog posts use their own SEO fields (title, description, OG image) and additionally publish Article + BreadcrumbList JSON-LD when the post is published and not hidden from search.

Photo detail pages (portfolio images)

When Enable Page View is on for a collection, each public photo URL can include ImageObject JSON-LD with:

JSON-LD field	Purpose
contentUrl / url	Image file and photo page URL
license	Link to your license text on /terms#… (from your legal templates)
acquireLicensePage	Same photo page (where visitors can license or buy)
copyrightNotice	© line with your business/name (maps to IPTC Copyright Notice)
creditText	Credit line for image search (maps to IPTC Credit Line)
license	URL to your license text on /terms#… (maps to IPTC Web Statement of Rights)
acquireLicensePage	Photo detail URL where visitors can license or buy
creator	Your studio as Organization
EXIF-related fields	Camera, lens, ISO, etc. when EXIF exists on the file

ArtInStack automatically injects this ImageObject JSON-LD metadata directly into your page HTML. This provides an explicit, machine-readable declaration of image licensing and creator attribution for Google and other search crawlers.

Two things are easy to confuse:

Metadata Mechanism	Handled on Photo Detail Pages?
IPTC-Mapped JSON-LD<br>(license, copyrightNotice, creditText, creator)	Yes — Automatically built dynamically from your user profile, assigned license templates, and media/portfolio configuration settings.
Embedded Binary IPTC Tags<br>(Internal JPEG/WebP/RAW byte blocks)	No — Not written to optimized asset files. To maximize global CDN performance, edge-delivered derivative formats strip internal image profile bytes. All rights data is declared via the structural HTML layer instead.

If a visitor downloads the image file, rights info travels with the file only if they embedded IPTC before upload or you use external tooling. For search and licensable-image discovery, rely on the live photo URL JSON-LD and your Terms page.

Configure photo detail and indexing: Photo detail pages. License copy: Media → Documents and public /terms on your site.

Impact map blocks

Map blocks on pages use portfolio geo settings; they do not add a separate page-level schema type. See Add an Impact map to a page.

How data flows (pages you edit)

[Page Settings: Meta title, description, OG image, Hide from search]
        → Save Page → Publish
        → Live HTML <head> (title, description, og:image, robots, canonical)
        → BreadcrumbList JSON-LD in page body
        → Listed in sitemap.xml (unless hidden)

[Portfolio photo detail — separate settings]
        → ImageObject JSON-LD on /photo/{id} URLs
        → License URL → /terms#{license_type}

Implementation steps

1. Open Pages → Edit → Page Settings.
2. Fill Meta title and Meta description for homepage, about, contact, and any landing pages you care about.
3. Set OG image on homepage and key campaign pages (1200×630-style assets work well).
4. Turn on Hide from search engines only for thank-you pages, drafts you must keep published internally, or duplicate thin pages.
5. Save Page → Publish → open the live URL in a private window.

For portfolio photos: open Portfolio Settings → Visibility & SEO and confirm Hide from search engines matches your intent.

Verify on your published site

Use the live or preview URL after save—not only the editor canvas.

1. View Page Source (fastest)

1. Open the public page (e.g. https://yourstudio.example/about).
2. View Page Source (browser menu) or DevTools → Elements → <head>.
3. Confirm:
   • <title> matches your Meta title (or sensible fallback).
   • <meta name="description" content="…"> matches your text.
   • <meta property="og:image" …> appears when you set OG image.
   • <meta name="robots" content="noindex, nofollow"> appears only when Hide from search engines is on.

2. Rich Results Test (structured data)

1. Go to Google Rich Results Test (or Schema Markup Validator).
2. Enter your homepage URL → expect BreadcrumbList and Organization (Organization may show as non-rich “valid” structured data).
3. Enter an interior page URL → expect BreadcrumbList.
4. Enter a photo detail URL (with Page View enabled) → expect ImageObject with license, copyrightNotice, and related fields when configured.

A “No rich results detected” message on a normal about page is common—meta + breadcrumbs still help indexing.

3. Social preview

Paste the URL into a share debugger (Facebook Sharing Debugger, LinkedIn Post Inspector, or similar) after OG image is set. Confirm the image and title match Page Settings.

4. Sitemap and Search Console

1. Open https://yourstudio.example/sitemap.xml in the browser.
2. Confirm important page URLs appear and hidden pages do not.
3. In Google Search Console, submit the sitemap property for your domain and request indexing for key URLs after major SEO changes.

Re-indexing can take days or weeks—that delay is normal.

Troubleshooting

Issue	What to check
Title in source does not match Meta title	Save Page and republish; hard-refresh; confirm you edited the published page
Page missing from sitemap	Hide from search engines may be on; page must be published
No ImageObject on a photo URL	Enable Page View in portfolio settings; photo must be reachable on your public site
License link 404 in JSON-LD	Publish license templates; open /terms on your live site
Duplicate titles across pages	Customize meta title per URL—especially homepage, about, contact

Related guides

• Page settings and overrides — slug, templates, chrome
• Photo detail pages — per-photo URLs, EXIF, sharing
• Portfolio geo visibility and impact maps — map pins and privacy
• Legal documents and templates — license text behind /terms links

Verifying your setup

• Homepage Meta title, Meta description, and OG image saved and visible in page source on the live URL.
• At least one interior page has unique meta fields.
• sitemap.xml lists published pages you expect indexed.
• One photo detail URL shows ImageObject JSON-LD in Rich Results Test (if you use Page View).