Resource icon

Thread SEO changes [Paid] 1.1.4

No permission to buy ($35.00)
Overview Updates (7) Reviews (1) History Discussion
For thread URL's I'll revisit this after Google has processed the changes that this addon introduces.

For XFMG there are the following type of redirects:
/media/123 → /media/full_tittle_here.123/
/media/categories/123 → /media/categories/full_tittle_here.123/
/media/comments/123 → /media/full_tittle_here.456/page-2#xfmg-comment-123
The latter is 83% of the XFMG redirects.


For XFRM:
/resources/full_tittle_here.123/review/110 → /resources/full_tittle_here.123/reviews#resource-review-110
/resources/full_tittle_here.123/reviews → /resources/full_tittle_here.123/ (when there are no reviews)
/resources/full_tittle_here.123/updates → /resources/full_tittle_here.123/ (when there are no updates or versioning has been turned off)
I wonder if this is a bug btw.

Xon said:
This will be from the XF image proxy service, I'm not sure what todo with that one; maybe an option not render those links for guests/robots?
Click to expand...
That seems best. I have just disabled it completely for now, as it currently seems to cause more harm than good with 40k spam links. I have no clue where on earth that comes from. Probably spammers somewhere linking their sites through our xenforo proxy.php
 
Interested in this but definitely waiting to hear more feedback from people already using it.
 
It is definitely working, but it takes time so don't expect results immediately. I installed it in Januari 2026:

1778748706231.webp

I also applied another fix to prevent Google from indexing completely useless URLs (from style variation):
K

Future fix Post in thread 'Google tries to crawl links from style variation chooser menu'

A less invasive option:

style_variation_macros

Code: 
<xf:macro name="variation_menu_item"
    arg-routeType="public"
    arg-route="{{ link('misc/style-variation') }}"
    arg-variation="!"
    arg-icon="fa-adjust"
    arg-label=""
    arg-selectedVariation="{$xf.visitor.style_variation}"
    arg-live="{{ false }}"
    arg-redirect="{{ null }}">

    <xf:set var="$tag" value="{{ $live ? 'span' : 'a' }}" />

    <{$tag} class="menu-linkRow {{ $variation === $selectedVariation ? 'is-selected' : '' }}"
        {{ !$live ? 'href="' . link_type($routeType, $route, null, {...
  • Like
 
Works great for pages with redirects. My chart looks the same as the above with hundreds of thousands resolved. So far just 57K left, but it keeps going down.
Blocked due to other 4.x.x issue has also gone down 90% after disabling link proxy.

There's still lots of technical issues to address, but this addon is great.

@Xon a feature that would also help significantly is to add lang=xx (language) html code settings per node so that threads get the proper language code. We have nodes in different languages. Google indexes all in English as that is the main board language set in xf. Therefore threads in those nodes are not ranking at all.
 
Alpha1 said:
Works great for pages with redirects. My chart looks the same as the above with hundreds of thousands resolved. So far just 57K left, but it keeps going down.
Blocked due to other 4.x.x issue has also gone down 90% after disabling link proxy.

There's still lots of technical issues to address, but this addon is great.
Click to expand...
Great to hear!

Alpha1 said:
@Xon a feature that would also help significantly is to add lang=xx (language) html code settings per node so that threads get the proper language code. We have nodes in different languages. Google indexes all in English as that is the main board language set in xf. Therefore threads in those nodes are not ranking at all.
Click to expand...
Adding a per node language option would be doable, but I'm unsure how to surface that in html. Sure there is a <p lanq=".." html attribute, but I haven't looked into how JSON-LD does multilingual support.

I don't think it would be too much effort, but please open a ticket if you are interested in funding it.
 
I decided to add a few template modifications to get it to work, as thats all thats needed:
  1. Template modification on PAGE_CONTAINER to get the proper output for language code if nodeID is in x,yz.
  2. Template modification on thread_view to get proper output for the $ldJson variable for language code if nodeID is in x,yz.
 
Is this a miss or an XF issue?

tagged users resolve to just the ID
1779412661146.webp
actual url: .com/members/ch..name.85/
 
briansol said:
Is this a miss or an XF issue?

tagged users resolve to just the ID
View attachment 338378
actual url: .com/members/ch..name.85/
Click to expand...
I've got another add-on which patches this behavior has as it has the metadata for mentioned users per post being tracked;
User Essentials X

User Essentials

Provide your members with additional username, thread, and post functions.

This vastly simplified implementing the feature without impacting performance (by requiring SQL queries per post)
 
You must log in or register to reply here.
Back
Top Bottom