This plugin has given every post (before installing the plugin) the same meta description as the first ever post. After installing the plugin, all posts created are correct.

How do I get posts (before installing extension) to have different meta descriptions and not all the first ever post?

a month later

So I noticed something weird when updating to .14 version. My website has in my region very good google search results. But before updating If I searched for the post it was there as a separate thing like it should be:

POST TITLE - FORUM TITLE (and link to the post)
DESCRIPTION

But now when I updateted, it just links to my forum and that's it in "description" if I could call it like that, it just says that post with similar title is on my forum...

FORUM TITLE (and link to the forum)
POST TITLE - TAGS

17 days later

just to say that the extension unfortunately doesn't work with beta 15

    Release 1.5.1 - Support Flarum beta 15

    This update should make this extension work with Flarum Beta 15. If you find any errors, please create an issue.

    Notice: This update is only for Flarum beta 15 or higher. You cannot install this update on Flarum beta 14 or lower.

    How to update?

    To update, run:

    composer update v17development/flarum-seo

    To install, run:

    composer require v17development/flarum-seo

    Updated interface

    Since the admin dashboard got a redesign, I've did the same happened to the SEO extension. All pages are now accessible via tabs instead of a dropdown menu. Looking fresh again 🙂

    a month later

    I installed it on localhost, so do I need to update the database also on a shared host?

    Or just need to upload all scripts again on the server?

    Please suggest, Thank you!

      Hey JasperVriends ! Have you ever thought about adding the possibility to add custom keywords for each post, same as in Wordpress?

        Thanks for effort @JasperVriends
        Is that possible to add custom title and description content for TAGS(flarum categories)
        I think it will be easier for us to focus on the SEO of our website.

        Best

          Gasjki Hi! Not yet, but in the extending the SEO extension documentation, there is a function which potentially could be used to update the page keywords. See section Updating the page keywords

          I think this would be a good idea, but I am also wondering if being able to set keywords per discussion is something that should be implemented into the SEO extension by default, or built in a separate extension hooking to the function setKeywords. Probably the SEO extension is the easiest, as we could also include functionalities as custom image and description.

          I would love to hear some opinions 🙂


          utasar Could you elaborate this a bit more? Also, don't forget to create an issue on GitHub: https://github.com/v17development/flarum-seo/issues

            JasperVriends I love the sound of key words being picked up out of every discussion! 😃

            Adding a voting system to the discuss? Discussions on search engines like google look better.

            • JAC likes this.
            a month later

            Release 1.6.0 - Do-follow links, external links in new tab & more

            In this version, new functionalities have been added! We've now implemented a 'do-follow' link management system. By default all Flarum links are set to nofollow. This will make sure people do not spam your forum with links to other domains in order to get more referrals.

            This update changes that! You are now able to add some domains to the do-follow list! This will prevent adding the nofollow attributes to the links which contain that domain. For more information about how this works, check out this knowledge base article.

            External links in new tab
            Another new feature is the external links in new tab functionality. As were already mapping trough the links for the nofollow feature, we made sure all external links open in a new tab. Internal links from your forum will still open inside the same window as usual.

            This unfortunately does mean that this extension now has a conflict with @010101 's elint extension.

            Twitter card size
            A new setting has been made available into the SEO settings tab: From now on you can set a Twitter card size when someone shares your community on Twitter. By default it is set to a large card. You can always switch back to the summary in the SEO settings.

            If you have any feedback or issues, let us know!

            Full changelog:

            • All external links are nofollow by default, but internal links are marked as do-follow
            • You can manage a do-follow links, excluding some external links to be marked as nofollow
            • All external links do now open in a new tab
            • Added twitter card size setting (default big)
            • Added Romanian language ( v17development/flarum-seo45 ), thanks @Gasjki for the taking the time to open a PR 🙂

            How to update?

            To update, run:

            composer update v17development/flarum-seo

            To install, run:

            composer require v17development/flarum-seo

            Do-follow list

              JasperVriends Very cool! Yes, uninstall elint before upgrading, everyone (if you use it). I’ll pop a disclaimer over on that thread. I won’t fully discontinue elint just in case for some strange reason someone doesn’t want to use this SEO extension, but they want the external/internal links feature. I don’t know why someone wouldn’t want this SEO extension, but you never know. 🤷‍♂️

              @JasperVriends When I opened the do follow settings for the first time it had my domain in there automatically which was a nice touch but it was typed in like this:

              ://www.seekadventure.net

              should I change it to:

              seekadventure.net

              I also just got this error in Sentry that looks related to do follow:

                JasperVriends This extension (or elint) should be able to specify the other in composer.json under conflicts, that would prevent both from being installed, which is easier than relying on people to remember.

                  MikeJones oh woops. No that's not necessary, it's just a placeholder generated via JavaScript for something that's automatically being added in the backend 😃

                  I'll fix the displayed domain in the next version 😛