Hi guys,

Any ideas on this?

currently using two different CloudFront domains.

I'm dumb ... What's a CloudFront domain?

I had the same question and I think that's why no one has suggestions yet.

Hi guys, thanks for your answers!

CloudFront is a CDN service provided by Amazon.

We currently have our images like this for the 1st website:

https://cloudfrontdomain1.cloudfront.net/.../website1/x.jpg

And like this for the 2nd website

https://cloudfrontdomain2.cloudfront.net/.../website2/x.jpg

Cloud front domains are formatted like this for exemple:

fds48erthra74pfd.cloudfront.net

We would like to use the same CloudFront domain for both websites. Like this for the 1st website:

https://cloudfrontdomain.cloudfront.net/.../website1/image.jpg

And like this for the 2nd website:

https://cloudfrontdomain.cloudfront.net/.../website2/image.jpg

We're talking about images, right? How exactly does that affect "SEO" (generally text based) in the traditional sense?

Secondly, what benefit is sought by introducing confusion?

Third, if all that is desired is to keep the images on ONE domain and serve two, that's done by embedding the full paths in IMG, which certainly looks like a "hijack" to anyone who takes a look.

Again, what is the END PURPOSE of seeking ONE when you obviously have TWO?

Thanks tangor for your answer.

It’s not just about images. We’re using CloudFront as a full CDN, so it also serves JavaScript files and stylesheets.

As for the websites, they offer the same service but are branded differently for two distinct markets. There’s a strategic balance between keeping them separate, while also showing some level of connection.

Why move to a single CloudFront domain? Mainly for cost efficiency and simplifying our technical architecture.

Color me confused. That's what sub.domains are for under an UMBRELLA COMPANY with different markets. OTOH I get the desire to cut costs, but CloudFront might not like getting played (two sites, one bill) and I suspect their TOS/Contract might have another opinion. Either one company with two markets, or two companies playing sly with one office/billing address. This does not fall into SEO territory---it is something else. The "risk" might be losing the hosting if not straightforward.

It’s the same company, and basically the same website, just branded differently for two distinct audiences.

I don’t personally see any issue with the setup, but to be honest, that part is more for the technical team.

I was mainly looking to get feedback from experienced folks here on the SEO side.

A CDN is used to provide downloads for files commonly used by many sites to improve page speed and reduce bandwidth usage.

So you only need one CDN and it doesn't make a difference which you use if it can provide the bandwidth for your targeted locations..

It’s the same company, and basically the same website, just branded differently for two distinct audiences.

I'm 99% about this, Google will view these as duplicate sites regardless of them supposedly for different audiences. This was a popular "trick" 20 years ago, I used it extensively across many cctlds until it no longer worked very well.

We would like to use a single CloudFront domain for both sites.

My gut feeling is to choose your more favoured site, 301 the second site, and promote that one site.

I have experimented with duplicate sites, they no longer work without major re-writes and different images.

Thanks Kendo and RedBar for your answers.

The two websites are not copies. They have different brand names and we focus on different SEO keyword targets for each.

Depending on the region or culture, people use very different terms to describe the same thing in our niche, and it’s simply not possible to target all those variations on a single website.

That’s basically why we’ve had two separate websites for over 10 years, without any indexing issues or penalties from Google.

I imagine many websites share the same CDN. But in our case, the question was really just whether merging our CDNs could raise any SEO concerns.

the question was really just whether merging our CDNs could raise any SEO concerns.

My only experience of using one domain (example a) to supply images across all my sites (example b, c, d etc) was, again, 15+ years ago and I stopped it because example a started to rank #1 for thousnds of niche trade-specific results when I wanted example b, c, d etc to be known for the widget source.

G pretty much recognises identical images.

If it’s purely about serving static assets (images, JS, CSS) from a single CloudFront distribution, there’s no direct SEO penalty. Google treats CDN assets as infrastructure, not a ranking signal.

Where it can get messy is in the details:

Cache or CORS mix-ups – if both sites pull files from the same paths without clean separation (like /site1/ and /site2/), you can get cache collisions or broken layouts that hurt CWV metrics.

Brand crossover – if you’re trying to keep the brands distinct, sharing a single CDN host can subtly link them together in Google’s eyes, especially if filenames, favicons, or structured data overlap.

Tracking noise – a shared CDN can mix up log data or cookie scopes unless you lock it down carefully.

So technically fine, but make sure your directory structure, versioning, and headers keep things clean. The bigger consideration is brand identity; I mean do you want Google (and users) to see the two as related? If yes, go for it. If not, two CloudFronts might still be worth the small extra cost for clarity.

Thank you very much, RedBar and White. Really appreciate your feedback.

We had two sites on different infrastructures and moved them under the same CloudFront. From an SEO perspective nothing really changed, as long as the domains stay separate and you don’t mix critical resources. The main thing is to avoid strange redirects or cache conflicts that might deliver the wrong content.