Search & Discovery·Guide
What Search Console is for
Search Console and Analytics answer two different questions. One tells Google your pages exist and lets you check whether Google agrees. The other tells you who showed up once they did. Photographers set up GA4 first because it's the familiar one, then treat Search Console as optional, and end up with beautiful visit charts on a site Google barely knows about.
At launch
Four things Search Console actually does
Verifies you own the domain
So Google will talk to you about it. Prefer a DNS TXT record at the registrar. An HTML file or meta tag dies when the host moves.
Accepts your sitemap.xml
A direct pointer to URLs you want crawled, faster than waiting for Google to find pages by following links. Submit it once; Google re-checks on its own.
URL Inspection
For one URL at a time: whether Google has it indexed, when it was last crawled, and why not if it doesn't.
Coverage and Performance
Indexing status and search impressions/clicks in aggregate, over time. A status window into what Google already decided, not a ranking lever.
It doesn't rank you for having an account
That's it. Search Console doesn't write descriptions. It doesn't count visits. It's a status window into what Google already decided, plus a way to hand Google a map instead of waiting for it to wander.
AI answer citations are a different scoreboard. See AI SEO myths for creatives. This page is the classic crawl-and-index path.
Verifying a site that might change domains
The usual advice is to paste a meta tag or upload an HTML file onto the site. That works until the host moves. A page starts on a platform subdomain, then you attach a custom domain and everything 301s over. File-based verification is tied to a specific hosted file. It breaks silently. A DNS TXT record verifies the domain, not a file, so it survives the switch.
Search Console treats the platform subdomain and your own domain as distinct properties either way. Verify the host people will actually search. When you move, add the new property rather than assuming the old one followed you.
The sitemap is a map, not every public URL
Checklists treat sitemap.xml as a complete inventory of everything a visitor can open. It isn't. ArtInStack generates one and keeps it current. You submit it once to Google; Google re-checks on its own. Republishing is not a resubmit ritual. The protocol that pings other engines at publish time is IndexNow, and it is a different job. See IndexNow, honestly.
What the map includes: the homepage, published pages and posts that are not hidden from search, a /terms URL on studio sites, and photo detail URLs (capped). What it currently doesn't: public galleries. Those URLs are still public. They just aren't in this file. Hidden pages and posts are omitted before Google ever sees them. A gallery's hide-from-search setting does not gate the photo URLs in the sitemap. Neither file is "every public URL."
Reading Coverage without panicking
A few things that look like errors and aren't: pages you've hidden from search won't appear as indexed. That's the setting working, not a crawl failure. A brand-new page can sit in "Discovered, currently not indexed" for days. Normal for a low-authority new domain. Submitting the sitemap speeds discovery; it doesn't guarantee same-day indexing. A page that used to be at a WordPress or Squarespace path and now redirects should show the redirect as intentional in Coverage, not as a broken link. That's what the import 301s are for.
What is worth investigating: a public, non-hidden page sitting in "Excluded" for reasons other than a redirect or your own noindex setting, weeks after publishing. That's the actual signal Coverage exists to give you.
Search Console vs. GA4/GTM
Worth stating plainly because it's the most common mix-up. Photographers install analytics first because it's the familiar product, then treat Search Console as optional. Neither substitutes for the other. Search Console tells you whether you're visible. Analytics tells you what happens after someone finds you. You configure Search Console at Google, on the canonical host. You configure analytics on the site, as visitor measurement.
| Job | Search Console | Analytics (GA4 / GTM) |
|---|---|---|
| Tells you | What Google knows about your site | Who visited and what they did |
| You configure it | At Google, on the canonical host | On the site, as visitor measurement |
| Data source | Google's crawl and index | Your site's own visitor traffic |
| Replaces the other? | No | No |
What this doesn't cover
Search Console also has a licensable-image report and a rich-results report for structured data. Both live in Google's product. If you're trying to understand image licensing signals specifically, see Licensable badge vs. IPTC.
Hand Google a map. Then check whether it used it.
Verify the canonical host, submit sitemap.xml, and keep GA4 for visits. IndexNow does not do this job.
Also in Guides: IndexNow, honestly · Hide from search, noindex, and private · AI SEO myths for creatives
