sybrew / the-seo-framework

The SEO Framework WordPress plugin.
https://theseoframework.com/
GNU General Public License v3.0
411 stars 46 forks source link

Premium CDN extension #79

Open oldegoodthings opened 7 years ago

oldegoodthings commented 7 years ago

Would love to have a full-featured sitemap (premium is okay) with all site pages (including product pages), images, and videos. Also possibly customizable to work with images from a CDN.

LeBaux commented 7 years ago

Are you the same person from here? In any case, @sybrew did a nice summary in that topic about the site map purpose. Check it out! May I ask why you need such a sitemap? As for the premium comment, I am afraid there simply is not going to be enough demand to justify developing it.

sybrew commented 7 years ago

There's actually a whole lot of demand for expanded sitemaps. Mainly for images, news, etc. However, Google's moving to Structured Data rapidly which renders them useless and incomplete.

Also, "premium" sitemaps don't truly serve the Premium SaaS project of TSFEM; which defies the reason why it's allowed on w.org in the first place.

Providing a CDN will be possible if there's enough income. CDNs are very expensive when serving loads of websites that might ignore the "fair use policy". This can be accounted for when there are enough subscribers; like with WordPress.com Jetpack Photon.

For the sitemap discussion, please continue on previous: #31

The CDN discussion can be continued here :)

Thanks!

sybrew commented 7 years ago

A CDN that's globally and readily available with correct GZIP and rewrite structure can massively reduce load times - ergo result in higher ranking because of lower bounce rate.

Although this doesn't cover SEO directly per se, it is, however, a major ranking signal and many hosting parties do this wrongfully and many sites can benefit from this.

From a marketing's perspective: It completely justifies the pricing.

Notes to self:

  1. Automated CDN pull-services require an endpoint. This might be a cause for concern. Capture how Proton (JetPack) has solved this?
  2. Add preconnect and prefetch meta tags.
  3. See if a fair-use policy needs to be evaluated through a bandwidth limit.
  4. Please note that CDN operation can be expensive. This idea might not ever see the light of day, and if it does the plug might be pulled if things go haywire (i.e. more operation costs than income).