Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEO audit #143

Open
iandunn opened this issue Dec 22, 2021 · 7 comments
Open

SEO audit #143

iandunn opened this issue Dec 22, 2021 · 7 comments
Labels
[Component] Content Issue in the site content, posts, pages, etc Help Wanted Extra attention is needed

Comments

@iandunn
Copy link
Member

iandunn commented Dec 22, 2021

Once WordPress/wporg-mu-plugins#38 is done (especially WordPress/wporg-mu-plugins#42), we should take a look to make sure there aren't any SEO regressions in the content areas.

Header/footers are covered by WordPress/wporg-mu-plugins#43

@iandunn iandunn added the Help Wanted Extra attention is needed label Dec 22, 2021
@iandunn iandunn added this to the Post-Launch Iteration 1 milestone Dec 22, 2021
bazza pushed a commit to WordPress/wordpress.org that referenced this issue Jan 7, 2022
@iandunn
Copy link
Member Author

iandunn commented Jan 28, 2022

@jonoalderson, do you have any interest in this?

The staging site is https://wordpress.org/news-test/

@jonoalderson
Copy link

jonoalderson commented Jan 28, 2022

Oooh, thanks for thinking of me @iandunn! Yes please; will explore!
Next week sensible?

@iandunn
Copy link
Member Author

iandunn commented Jan 28, 2022

Definitely, thanks!

@jonoalderson
Copy link

Looking good! Just a few SEO concerns:

  • We already have thin+duplicate category issues (e.g., see https://wordpress.org/news-test/category/development/ vs https://wordpress.org/news-test/category/releases/). Should these really be categories? I think it'd make more sense semantically for them to be tags, and, for us to noindex all tag pages. Regardless, let's take a critical look at all of the taxonomy types and members, and determine what should be consolidated/indexed/noindexed.

  • What's happening to all the old/existing blog/news content? Do we have a migration or retirement strategy?

  • What does the international setup look like? I don't see any hreflang tags.

And some performance issues:

  • Some of the images in the "People of WordPress" section have enormous file sizes. Are we missing processes to optimize these before/on upload?

  • We should compress those big SVG files, too.

  • Can we ditch the remote Google Fonts call, and host+serve them locally?

And some UI issues:

  • On larger screens, the blue paint ribbon starts to occlude links. See screenshot.
    image

  • It's not immediately obvious how I navigate up from / out of a given blog post, and there's only limited lateral navigation at the end of the post. I worry that we'll confuse people who arrive directly on these pages without context, get confused/stuck, and leave (and how that'll harm our SEO). This is especially apparent on larger screens where the navigation elements are all way out of the field of view, in the far corners.
    image

@coreymckrill
Copy link
Contributor

Thanks for taking a look @jonoalderson, this is helpful. I don't have answers to all of the above points, but a few followups:

What does the international setup look like? I don't see any hreflang tags.

My understanding is that for now, the scope of this new design is only the English version of the News site. There will be future efforts to make it functional for rosetta sites, e.g. es.wordpress.org/news.

It doesn't look like the current News site has hreflang tags either. I suppose the ideal would be to have one for each rosetta site that also has a news section? I'm not sure the best way to accomplish that, but it might be worth opening a Meta Trac ticket, as that would be outside the scope of this theme in particular.

We should compress those big SVG files, too.

Seems like a good idea. Opened a separate issue for it here: #285

Can we ditch the remote Google Fonts call, and host+serve them locally?

Not sure why we're not doing that already, but definitely worth discussing: #286

It's not immediately obvious how I navigate up from / out of a given blog post, and there's only limited lateral navigation at the end of the post.

@beafialho any thoughts on this?

@beafialho
Copy link
Collaborator

It's not immediately obvious how I navigate up from / out of a given blog post, and there's only limited lateral navigation at the end of the post. I worry that we'll confuse people who arrive directly on these pages without context, get confused/stuck, and leave (and how that'll harm our SEO). This is especially apparent on larger screens where the navigation elements are all way out of the field of view, in the far corners.

@coreymckrill @jonoalderson besides post navigation down at the bottom of the posts, there's the Global Header - that gives users access to any part of WordPress.org and Search - and Local Navigation Bar containing all the blog's categories, including "All Posts", which contains every post from every category in chronological order. Also, they're sticky to make all this process much more immediate. That said, if you're in a blog post, it should be really easy to navigate both back to the News homepage, or to a different category. Here's a quick video showing what I mean:

navigation.mp4

@coreymckrill coreymckrill added the [Component] Content Issue in the site content, posts, pages, etc label Feb 17, 2022
@syedhasibulalam

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Component] Content Issue in the site content, posts, pages, etc Help Wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants