Use this checklist to find, assign, fix, and verify photography SEO issues

This checklist works best for photographers with an existing website who want to improve their Google rankings without hiring an agency. If you're building from scratch, use this to guide your platform choice and initial setup.

The tactics here apply across wedding, portrait, commercial, and product photography. Local photographers targeting a specific service area will get the most immediate wins from the NAP and Google Business Profile sections.

If your website is built on Squarespace, Showit, or WordPress, you'll find platform-specific guidance later in this checklist. Custom-built sites can adapt these steps by working with your developer.

Before optimizing for rankings, your website needs to be fast and crawlable.

• Measure page speed: Run your homepage and a portfolio page through Google PageSpeed Insights. Image-heavy sites often slow down here. Document your baseline - you'll compare this later. Evidence: save the report for the homepage plus a representative portfolio or service page. Pass: the pages render reliably and no major image, script, or layout issue makes the experience unusable. Fail: repeated loading problems, severe layout instability, or a clear bottleneck remains. Severity: high when booking or portfolio pages are materially impaired. Owner: site owner, designer, or developer. Corrective action: isolate the heaviest assets or scripts and reduce the specific bottleneck. Validation: rerun the same URLs and compare the evidence.
• Check mobile responsiveness: Open your website on a phone. Tap images and buttons. If anything breaks or lags, that's a mobile usability issue to fix now. Evidence: test navigation, gallery interactions, forms, buttons, and text on the core pages. Pass: the full booking path works without hidden controls or broken layouts. Fail: a user cannot reliably view work or contact the photographer. Severity: high on money pages. Owner: designer or developer. Corrective action: fix the affected layout or interaction. Validation: repeat the same task on the same device class.
• Audit your robots.txt: Visit yoursite.com/robots.txt. It should not block /wp-content, /images, or your portfolio paths. For Squarespace and Showit, this is usually managed automatically. Pass: important public pages and required resources are not blocked. Fail: a rule prevents intended crawling. Severity: critical when it blocks core content. Owner: developer or technical site owner. Corrective action: remove the unintended block. Validation: fetch the file again and test the affected URL.
• Install Google Search Console: Verify ownership and check for crawl errors in the Pages report. Fix any 404s on portfolio pages. Evidence: review indexed, excluded, and error URLs, including any 404 reports. Pass: important pages are discoverable and broken URLs are understood. Fail: valuable portfolio or service URLs are missing or broken. Severity: high for important pages. Owner: SEO or developer. Corrective action: restore, redirect, or remove links to broken URLs as appropriate. Validation: inspect the corrected URL and monitor the report after recrawl.
• Enable HTTPS: Your URL should start with https://. If not, upgrade your SSL certificate immediately. Pass: the site resolves securely without certificate errors, and internal navigation does not send visitors to insecure variants. Fail: insecure or mixed variants remain accessible in normal navigation. Severity: high. Owner: host or developer. Corrective action: correct the certificate, canonical host behavior, and internal links. Validation: reload core pages in a clean browser session.

Skip any of these? Your SEO improvements won't compound later. These take 30 minutes total.

Photography websites live or die by image optimization. Google can't see your images the way clients do - it relies on alt text, and your pages need compressed files and smart loading strategies.

For every portfolio image:

• Write descriptive alt text: "Portrait of bride and groom at sunset" is better than "IMG_4521.jpg" or "wedding photo." Include your service type when natural: "Headshot photography of business professional in studio." Aim for 8-15 words. Evidence: inspect the rendered alt attribute and the image's purpose on the page. Pass: informative images have concise text that describes the visible subject and context, while decorative images are handled appropriately. Fail: the field is empty when meaning is needed, duplicates surrounding copy, or contains a filename. Severity: medium for accessibility and content clarity. Owner: photographer or content editor. Corrective action: write an accurate description tied to the scene and service when relevant. Validation: inspect the rendered HTML again.
• Compress without losing quality: Use Squoosh (web-based) or ImageOptim (Mac). A wedding photo should be under 200KB on web. Many photographers serve 2-5MB images - this tanks your page speed. Evidence: record transferred image sizes in the browser network panel. Pass: files are appropriately compressed for their displayed dimensions and visual role. Fail: unnecessarily large originals are served to typical visitors. Severity: high when image payload makes up most of the weight of important pages. Owner: photographer, platform configuration, or developer. Corrective action: resize, compress, and serve responsive derivatives. Validation: compare transferred bytes and visual quality after publishing.
• Use descriptive filenames: Rename files before uploading. "bride-groom-outdoor-portrait.jpg" beats "photo-123.jpg." This is a small signal but can compound across 50+ portfolio images. Evidence: review file names before or after upload. Pass: names are readable and maintainable where the platform preserves them. Fail: the media library is full of opaque labels with no internal production value. Severity: low. Owner: photographer or content editor. Corrective action: use a consistent descriptive naming convention for new assets. Validation: check the media library and rendered asset URL where applicable.

Platform-specific image hosting: Squarespace and Showit handle image compression automatically. WordPress doesn't - use Smush or ShortPixel to compress on upload. Document how many images you've optimized (e.g. "47 portfolio images compressed - reduced homepage load time from 4.2s to 2.1s").

How you organize your portfolio directly affects which keywords you rank for. Two approaches exist: gallery-based (all work in one page) or single-image pages (one image per page with dedicated text).

Gallery-based approach (Squarespace/Showit default): One Portfolio page contains 20-50 images with filter tags. Fast to set up. Harder to rank for specific keywords like "wedding photography Boston" - Google sees it as one general portfolio page, not 10 service-specific pages. Evidence: review the main gallery, its internal links, headings, filters, and the search intent it is expected to satisfy. Pass: the gallery clearly represents a coherent service and routes visitors to deeper information. Fail: unrelated work is mixed together and the page offers no useful context for a client comparing services. Severity: medium. Owner: photographer or content lead. Corrective action: separate genuinely different services or intents. Validation: confirm each important service has an obvious destination and internal path.

Single-image pages (WordPress advantage): Each image gets its own page with 200-300 words of supporting text. Slower to produce but ranks for more keywords. Example: /portfolio/jennifer-mike-wedding-boston with descriptive text about the couple, location, and service type. Evidence: inspect pages that exist primarily for a single project or image. Pass: the text is genuinely useful, specific to the project or service, and worth indexing. Fail: thin copy has been created merely to multiply URLs. Severity: medium to high when thin pages are widespread. Owner: content lead. Corrective action: enrich, consolidate, noindex, or remove low-value destinations based on their purpose. Validation: review the final page set for unique intent and useful evidence.

For most photographers: Start with gallery structure on your main portfolio. Create 3-5 additional standalone pages for your highest-value services (e.g. /wedding-photography, /corporate-headshots). Each standalone page includes 4-8 portfolio images, 300 words of text describing your approach, and a clear call-to-action. Evidence: list the photography services that materially differ in audience, deliverable, or buying intent. Pass: each important service has enough original information to help a buyer decide. Fail: pages are duplicated, vague, or disconnected from representative work. Severity: high for core revenue services. Owner: photographer and content editor. Corrective action: create or consolidate pages around real service intent. Validation: check the page against the enquiry questions clients actually ask.

Page structure within each portfolio page: H1 should match your service type and location if relevant ("Wedding Photography in Boston"). Include a photo gallery, 1-2 testimonials, your process or approach, and a contact button. End with an FAQ relevant to that service. Pass: the heading accurately describes the service and location when relevant, the portfolio evidence matches the offer, and the enquiry action is clear. Fail: the page title, work shown, and booking path contradict each other. Severity: high on important service pages. Owner: content editor. Corrective action: align the page around one clear service decision. Validation: reread the page as a prospective client and verify every section supports that decision.

Schema markup tells Google what your website contains in a language it understands. For photographers, two schemas matter most: LocalBusiness and Service.

LocalBusiness schema: Add this to your homepage or About page. It includes:

• Your business name
• Phone number
• Address and service area (geo radius or list of cities)
• Business type ("Photographer")
• Hours of operation (if you take bookings during specific times)
• Image of you or your studio

LocalBusiness markup check: Inspect rendered structured data where the business entity is represented. Confirm that business details agree with visible information and real operations. Remove unsupported properties and validate the final output with a schema validator.

Service schema: If you book clients directly through your website, Service markup describes the services clients can book. Include service area, rates (if public), and areas served. Service markup check: compare service-related structured data with the visible service page, keep only supported properties, and confirm the output matches the rendered page.

How to add it: Squarespace doesn't expose schema controls directly. Showit has limited schema options. WordPress users can use RankMath or Yoast's Local SEO add-on to add LocalBusiness schema, or paste schema JSON in your homepage HTML.

If you can't add schema directly, your platform may still send some signals to Google - but adding it manually improves clarity. Validate your schema using Google's Rich Results Test after implementation.

NAP stands for Name, Address, Phone. Consistent NAP details across your website, Google Business Profile, and local directories help confirm your business exists and support your local rankings.

Audit your NAP: Search a spreadsheet for your business name. Write it exactly the same way everywhere:

• Homepage header
• Footer
• About page
• Contact page
• Google Business Profile
• Google Maps
• Photography directories (WeddingWire, The Knot, Yelp, etc.)

Evidence: create one reference record for the business name, eligible public address when applicable, phone details, website, and core service description, then compare it against each of those places. Pass: each active listing clearly describes the same business. Fail: old locations, conflicting names, duplicate profiles, or disconnected phone details could mislead a client. Severity: high when contact or location data is wrong. Owner: business owner or local SEO lead. Corrective action: update authoritative profiles first, then remaining listings. Validation: repeat the comparison after updates publish.

If your homepage says "Sarah Chen Photography" but your GBP says "Sarah Chen Photographer," that's a mismatch. Standardize to one version and update all instances.

Build citations in high-authority directories: Being listed in The Knot, WeddingWire, Yelp, and local Chamber of Commerce sites can signal legitimacy to Google. Complete your profiles with identical NAP, photos, and service descriptions. In our experience, photographers adding their NAP to 5-10 relevant directories see measurable improvement in local map pack rankings within 6-8 weeks. Evidence: list the platforms relevant to the photography niche and market, then confirm each profile is accurate, maintained, and useful for discovery or reputation. Severity: medium when important profiles are inaccurate, low when a marginal directory is absent. Owner: business owner or local SEO lead. Corrective action: correct or retire inaccurate listings and prioritize platforms clients actually use. Validation: revisit the live profiles and compare them with the reference record.

Claim your Google Business Profile (if you haven't): This is non-negotiable. Even if you're not local-service focused, a claimed GBP can give you a knowledge panel on Google and a place for Google to verify your phone number and address. Pass: name, phone number, website, category, address or service-area configuration, and visible service information reflect real operations. Fail: the profile is unclaimed, inaccurate, duplicated, or represents a location the business does not legitimately operate. Severity: high for local discovery. Owner: business owner. Corrective action: correct the profile according to platform eligibility and business facts. Validation: review the live public profile after changes are approved.

Squarespace: Strong defaults for image compression and mobile responsiveness. Limited schema and alt text controls. Portfolio galleries are gallery-based (hard to create service-specific pages). Workaround: Use custom code blocks to add schema JSON to your homepage and alt text to images via their native editor. No robots.txt access, but Squarespace blocks nothing by default. Evidence: inspect how the current template handles image derivatives, alt attributes, title fields, canonical tags, redirects, and structured data. Pass: the required photography pages can be edited and validated without contradictory output. Fail: an important field is inaccessible or generated incorrectly. Severity: depends on the affected check. Owner: site editor or developer. Corrective action: use supported platform controls before adding custom code, and document any custom override so it can be retested after template changes.

Showit: Built for photographers with drag-and-drop portfolio builders. Good mobile performance. Minimal SEO controls compared with WordPress. Check the alt text, title tag, and schema options available in your current build. If using Showit, expect to handle some SEO control through Showit's custom code block (limited). Consider this if you plan heavy SEO investment. Pass: core pages expose enough control to meet the technical and content checks in this audit. Fail: a platform limitation prevents a required fix or makes maintenance unreliable. Severity: medium to high depending on scope. Owner: designer or developer. Corrective action: use the platform's supported fields where possible and document any custom-code dependency before further investment.

WordPress with a photography theme (Neve, Astra, Soledad): Maximum SEO control. Alt text fields on every image. Full schema support via Yoast SEO or RankMath. Slower out of the box but most powerful if configured right. Requires basic technical comfort or a developer. Recommended for photographers planning service-specific pages beyond portfolio galleries. Evidence: inspect theme output, image settings, caching, plugins, alt fields, canonical tags, and any structured-data generators. Pass: plugins and theme responsibilities are clear and do not conflict. Fail: duplicate functions, heavy assets, or competing markup create inconsistent output. Severity: high when the conflict affects crawling, performance, or important pages. Owner: WordPress administrator or developer. Corrective action: simplify the stack and assign one source of truth per function.

All platforms: Focus first on page speed (Phase 1), then image alt text (Phase 2). Platform differences matter less than execution on these two.

Week 1: Technical evidence

• ☐ Run homepage and portfolio page through PageSpeed Insights. Document baseline score. Pass when the main experience is usable and major bottlenecks are identified; owner: developer or site owner; fix the specific bottleneck; validate by rerunning the same pages.
• ☐ Test mobile responsiveness (open on phone, tap elements). Pass when galleries, navigation, forms, and buttons work along the enquiry path; owner: designer; fix broken interactions; validate on the same device class.
• ☐ Visit yoursite.com/robots.txt and confirm it's not blocking portfolio paths. Owner: developer; correct the rule; validate with a fresh fetch.
• ☐ Install Google Search Console and verify ownership. Classify important index or crawl issues.
• ☐ Check for 404 errors in the GSC Pages report. Fix any broken portfolio links. Severity is high when users or crawlers are sent to dead destinations; owner: developer or content editor; restore, redirect, or remove the source link; validate the final response.

Week 2-3: Image evidence

• ☐ Compress all portfolio images (target: under 200KB per image for web). Inspect the transferred size of representative portfolio assets.
• ☐ Rename image files to descriptive names (bride-groom-outdoor-portrait.jpg). Pass when new assets follow a maintainable convention rather than opaque production names.
• ☐ Write alt text for 20 key portfolio images. Use 8-15 words describing the scene and service type.
• ☐ Re-run PageSpeed Insights. Compare to Week 1. Target improvement: 0.5-1.5 second faster load time. Use the same test conditions as in Week 1.

Week 4: Portfolio and service structure

• ☐ Decide: gallery-based or single-image portfolio approach (see Phase 3 for tradeoffs). Make sure the gallery and any individual project pages each serve a distinct purpose.
• ☐ Create 3-5 standalone service pages (e.g. /wedding-photography, /headshots). Add 300 words and 4-8 images to each. Each page should answer a real service decision.
• ☐ Write or update homepage and About page H1 tags. Include location and primary service type where relevant. Check every important H1 against the service and location actually represented on the page.

Week 5: Structured data and local identity

• ☐ Add LocalBusiness schema to homepage (or use Yoast/RankMath plugin if on WordPress). Compare it with visible business information and remove unsupported properties.
• ☐ Audit NAP across your website. Standardize spelling and format everywhere. Compare the website, profiles, and active listings against one business-information reference record.
• ☐ Claim or update your Google Business Profile. Add photos, service areas, and hours. Review the category, contact details, and service information for accuracy.
• ☐ Validate schema using Google's Rich Results Test. Record errors or warnings that require action.

Week 6: Relevant listings

• ☐ Add your NAP to 3-5 photography directories (The Knot, WeddingWire, Yelp, local Chamber of Commerce). Prioritize directories that are relevant to the business and that you can keep accurate.
• ☐ Make sure directory listings match your homepage NAP exactly. Recheck live listings after changes publish.

Ongoing checks

• ☐ Write alt text for new portfolio images as you upload them.
• ☐ Compress new images before uploading. Check what the platform actually serves after upload.
• ☐ Monitor GSC monthly for new crawl errors or indexing issues.
• ☐ Check PageSpeed monthly to catch speed regressions. Retest representative pages after design, plugin, theme, or gallery changes.

Image optimization is where most photography websites lose rankings. The good news: it's fixable in 2-3 weeks with the right tools.

Compression tools:

• Squoosh (free, web-based): Upload an image, set quality to 75-80%, export as WebP. Typical result: a 4MB JPEG becomes 200-400KB WebP with no visible quality loss. Fast and requires no software installation. Evidence: export a representative image with several settings and compare both file weight and visible quality. Pass: the smaller derivative preserves acceptable visual detail for its display size. Fail: compression creates visible artifacts or the output is still unnecessarily large. Owner: photographer or content editor. Validation: compare the published asset in the browser.
• ImageOptim (Mac, free): Drag and drop a folder of images. Removes metadata and compresses losslessly by default. It runs fully automatically. Evidence: compare a copy of the original file before and after optimization. Pass: metadata or encoding overhead is reduced without harming the required output. Owner: photographer. Validation: compare file size and rendered image.
• Smush (WordPress plugin, free tier): Automatically compresses images on upload. Recommended for WordPress photographers adding images regularly. Evidence: inspect what the plugin generates on upload and whether responsive sizes are served. Pass: derivatives are created and the live page delivers appropriate files. Fail: originals still make up most of the network payload. Owner: WordPress administrator. Validation: inspect the network response after upload.

Benchmarks for photographers: Industry benchmarks suggest portrait images (headshots, wedding photos) should be under 150KB on web for fast loading. Product photography or high-resolution detail shots can be 200-300KB. If your homepage loads in over 3 seconds, image compression is usually the culprit.

Lazy loading: This tells browsers to load images only when users scroll near them, not all at once. Squarespace and Showit enable this by default. Test by opening DevTools (F12 on Chrome) and watching the Network tab - images should load as you scroll, not all upfront. Pass: offscreen images are deferred and the visible lead image is not delayed in a way that harms the experience. Fail: the gallery loads unnecessary offscreen assets immediately or a critical visible image is deferred incorrectly. Severity: medium to high on image-heavy pages. Owner: developer or platform administrator. Corrective action: use native browser lazy loading or a compatible implementation and exclude critical images when required. Validation: repeat the network test.

WebP format: Newer format that's 25-35% smaller than JPEG with same quality. Most browsers support it now. Use it for portfolio images. Keep JPEG as fallback for older browsers (most tools handle this automatically). Evidence: inspect the actual response format and fallback behavior across supported browsers. Pass: modern formats are served where they reduce transfer size without harming compatibility or presentation. Fail: format conversion breaks image delivery. Owner: developer or platform configuration. Validation: compare file transfer and rendering on the browsers you support.