A wedding photographer’s site is built to be looked at: dense galleries, an inquiry form, often a pop-up offering a pricing guide. Each of those three features is also a place where technical SEO quietly breaks, and a beautiful Atlanta wedding site can rank poorly precisely because of the things that make it beautiful. The galleries slow it down, the pop-up trips a mobile penalty, and the form hides content the crawler never sees. The fixes are specific to each, and worth separating.
| Feature | The technical risk | What addresses it |
|---|---|---|
| Galleries | Heavy images push LCP past 2.5s | AVIF/WebP, correct sizing, lazy-load below the fold |
| Pop-ups | Full-screen overlay on arrival from search | Exit-intent or small dismissible banner |
| Submission forms | Scroll-loaded or thin pages the crawler misses | Content in the initial DOM, noindex thank-you pages |
Galleries are where a wedding site earns its slowness. The largest image in the viewport is usually what Google measures as Largest Contentful Paint, one of the three Core Web Vitals, and the threshold for a good score is 2.5 seconds at the 75th percentile of real visits. A gallery-heavy homepage is the hardest kind of page to keep under that line. The work is to serve images in modern formats like AVIF or WebP, size them correctly for the device rather than shipping a 4000-pixel file to a phone, and lazy-load the images below the fold so they load only as someone scrolls. One exception matters: the lazy-load attribute is never applied to the LCP image itself, because deferring the main image delays the very thing being measured. Core Web Vitals act as a tiebreaker between pages of similar quality rather than a magic lever, but in a market as crowded as Atlanta wedding photography, the tiebreaker is often where the ranking is decided.
The pop-up is the feature most likely to cause an actual penalty. Since January 2017, Google has down-ranked pages that show an intrusive interstitial, a pop-up covering the main content, when a visitor arrives directly from a mobile search result, and that policy is still in force as part of the page experience system. The trigger is narrow and worth understanding. It is the overlay on the first landing from search that counts, not pop-ups that appear later in a visit, and several kinds are explicitly exempt, including legally required notices like cookie or age prompts, login dialogs for private content, and small banners that are easy to dismiss. A pricing-guide pop-up can stay, but it is safer as an exit-intent overlay triggered when someone moves to leave, or as a small banner using a reasonable share of the screen rather than a full-screen gate on arrival. Recovery from the penalty requires removing the interstitial and waiting for the page to be re-crawled.
The submission form raises a subtler issue: what the crawler can actually see. Google renders JavaScript in two steps, crawling the raw HTML first and then rendering the page in a headless browser, but its rendering service uses a fixed viewport and does not scroll, so anything loaded only on scroll, a gallery section or a form that appears as the visitor moves down the page, may never fire during rendering. The safeguard is to keep the content that matters in the initial rendered DOM rather than behind a scroll trigger. The thank-you page a form sends visitors to is the other piece. It is usually thin, near-identical across submissions, and carries no search value, so it is typically set to noindex to keep it out of search results. Forms built with hash-based routing are not reliably crawlable either, and a reCAPTCHA, while useful against spam, adds JavaScript that can weigh on Interaction to Next Paint, the responsiveness Core Web Vital with a 200-millisecond target.
None of this changes the design of a wedding site; it changes whether the design survives contact with a search crawler. The galleries, the pop-up, and the form can all stay, as long as the images are light enough to load fast, the overlay does not block the first thing a searcher sees, and the form does not bury the page behind a scroll or a thin redirect. A wedding site sells the look of it, and the technical layer underneath is what decides whether that look ever loads for the Atlanta couple searching for it.