Hi.
Please complete or add this features in the plugin.

• Global Metadata
• Website Identity
• Contacts
• Social profiles
• Verify Ownership
• Customization: Example Site title (- \ |) Article title or page or collection.
• Robots
• Robot.txt
• Sitemaps
• shema.org
• Dublin core.

Tks

Any plans for Structured Data Support?

My SEO Pro lacks "translation" several places: cp.settings (left navigation), SEO Pro cp.settings (H1 at settings page), Addons.SeoPro::messages.report Is Being Generated, Addons.SeoPro::messages.back To Reports and so on.

Statamic 2.10.5
SEO Pro 1.0.3
Full locale da_DK

All other separators do though.

I'm currently doing the following in custom controllers:

datastore()->merge([
    'seo' => [
        'title' => htmlspecialchars($entry->name),
        'description' => htmlspecialchars(str_limit($entry->description, 250)),
    ],
]);

This works, of course - but not with the cannocial URL, alternate_locales and last_modified because it gets overriden in your TagData class 😄

So, a cleaner way to override the SEO stuff would be nice :-)

In the first versions of the addon (and as per the screenshots on Marketplace), the list of fields in the select box to set for a property showed the pretty display: value for the field. It now shows the file name which is not always as helpful.

In a discussion with Jack, he said this was a bug (at the same point as diagnosing asset fields not showing in the field list), but I don't think it was ever recorded. It would be nice to see the label again rather than the fieldname.

In addition, because the list of fields is seemingly drawn from across different fieldsets, it would be helpful to show which fieldset it was being drawn from for cases where there are similarly named fields.

We're having a lot of DB content and custom controllers here and we just installed the SEO Pro Addon for testing. Very nice thing though, but it would be nice, to have the possibility to set a custom image URL to use as meta image 😄

Another great feature for SEO Pro would be a simple interface to redirect legacy URLs to new pages. Much better than trying to build out in .htaccess file.

By now anything we add to this field will be shown for all locales. But we need different site names for each locale. The problem will be solved If we can use localizable global variables like {{site_name}}.

If my keyword target is "pink gondolas" and I don't mention that on my page I should get a warning.

If I have the keywords in my title, meta description and with a good frequency in my content then I should get a thumbs up.

Bonus points for multiple keywords and synonyms!

Entering | as the separator in the CP saves in the seo_pro.yaml file as
site_name_separator: | which doesn't conform with yaml formatting. You have to manually enter '|' or "|" in seo_pro.yaml in addon settings to get it to work.

I personally think the home page of a website doesn't need to have the title ie Home as it's pretty well obvious...

I used to be able to handle this using this kind of code in my default layout:

<title>{{ if title != "Home" }}{{yield:title}}{{ title or site_title }}{{/yield:title}} &mdash; {{ /if }} My Rad Website</title>

Which would give me this:

My Rad Website = nice

instead of

Home — My Rad Website = ugly

Can we add an option to hide the title if its the Home Page?

How would somebody set the meta data for a non-page/entry driven url? Would something like this work? Or can/does it fall back to the cascade at all?

/landing:
  template: landing-page
  seo:
    title: Super Cool Landing Page

Hey there,

I'm fairly new to statamic. Perhaps I'm doing this all wrong.

There is a collection for testimonials, which don't intended to be a site on its own.
The SEO Report Generator always says I should have Meta Descriptions for this collection. Is there a way to disable SEO for a collection?

Bye,
— Alexander

The new option to disable meta title is very useful to get a clean title on home page.
But it's actually also disable og:title which is equal to null in the head.

I think og:title should have the same value as meta title in this case.

The combination of 'Site Name' and 'Meta Title' gives meaningful titles for pages (i.e. About Us | Company XY), but could lead to a duplicate mention of the company name on the homepage (i.e. Company XY | Company XY). It would be useful to disable the 'Site Name' (and the Site Name Separator too) only on the homepage.

It's already possible to disable the 'Meta Title' per page, but that gives you a blank og:title, see #51. As well as to disable the 'Site Name' global for all pages. But a more fine tuning way how to handle the title on the homepage would be useful.

So if meta value is empty, lets not display that. This way section/yield be used easily.

On our .staging site, the Seo Pro section in the cp is not showing all the plugin pages:

Whilst locally, it is showing all the sections:

We have purchased the license. Is this because the site is .staging and not the license's domain?

Hello,
I have a problem in my prod env.

1. The menu don't display in the cp, only show the report.
2. I have a error in the sitemap.xml, the page return this alert

Whoops, looks like something went wrong.
2/2
ErrorException in 31e3a2381381a5b5899d9b6bdcf0b778 line 2:
Parse error: syntax error, unexpected 'version' (T_STRING) (View: site/addons/SeoPro/resources/views/sitemap.blade.php)

Version statamic: 2.10.2
PHP: 7.2.x
OS: Ubuntu 18.04.

Tks

Pretty weird. Not sure if this is on the SEO Pro side, or the core side.

We are getting "the page object" by getting the id from context. On routes, there's no such thing.

We can probably fix this on the Statamic side by passing some sort of page_object into the context which could be the Page/Entry/etc or a Route.

What is the best practice for 404 pages?
What sort of data should be used in meta tags etc?

On our site, we need to edit the specific line: <link rel="alternate" href="{{ url }}" hreflang="{{ locale }}" />. We also need to have this "outside" of alternate_locales.

In meta.html, it is like this:

{{ alternate_locales }}
<link rel="alternate" href="{{ url }}" hreflang="{{ locale }}" />
{{ /alternate_locales }}

However, we do not want to list the alternate locale hreflang, we want the current locale instead.

I assume we'd have to "monkey patch" meta.html? Or can we somehow override it somewhere else?

please add content analysis to the plugin as well. It would be nice to see analysis right from the page or blog post.

Noticed this after getting an error via the Google Search Console.

Upon testing and setting up the SEO PRO add-on on our Statamic page I've stumbled upon a bug when you select a custom image field on a collection item for SEO. While it works fine on default language it breaks when you select any other locale supported on the page.

Default link generated using {{ seo_pro:meta }} in layouts file:
https://statamic.test/img/asset/bWFpbi9sanVibGphbmEtYmcuanBn?p=seo&s=70949a94ecdfcc6cebbb392684d02382

Link generated on the nondefault locale:

https://statamic.test/en/en/img/asset/bWFpbi9sanVibGphbmEtYmcuanBn?p=seo&s=70949a94ecdfcc6cebbb392684d02382

The issue is there in double /en/en in between which doesn't work.

Even without changing anything I get the "are you sure you want to leave" popup.

Hey,

I had the use case where I would want to hide pages from google (see #19).
Then the pages shouldn't appear in the sitemap.xml.

Toggle in the SEO Tab could do the trick.

What do you think?

It would be great if you could add a simple select fields (or checkboxes) for meta robots. Could easily fit in the SEO Tab.

<meta name="robots" content="noindex, nofollow">

noindex, nofollow
noindex
nofollow
index, follow (default)

I had the use case, where I wanted to hide pages from google with the "noindex, nofollow" tag.

as the title says, default hreflang tag should be present along with the other languages.

For example, if you see this:

It would be cool if you could click it to filter down to those 7 pages.

If you have a bunch of other failures, it's difficult to know which are failing that specific check.

Probably take the first image?

It would be nice if the SEO add-on's fields could be a sidebar, or included as a partial to have a bit more control over where it is placed - instead of it always being it's own tab at the top.

We have installed the SEO Pro addon, everything is working great! However, the generated sitemap.xml outputs ~50 references to the homepage…

// this URL block is repeated ~50 times
<url>
    <loc>http://thoughtandmortar.local/</loc>
    <lastmod>2018-05-15</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.5</priority>
</url>

(Also tested on our 'live' server, same result)

In the addon settings, under Tools > SEO Pro > Site Defaults, I have disabled SEO Pro for any Collection that does not directly output it's own page/URL, which did not change the output.

All other page/URL references in the generated sitemap.xml a correct.

Has anyone else encountered this, or have any bright ideas on a possible fix?

:)

Just trying to run my first report. The UI was hanging so I tried the command line

php please seo:report:generate
Generating...
[Symfony\Component\Yaml\Exception\ParseException]  
The YAML value does not appear to be valid UTF-8.

I imagine this error is something to do with my site and not the plugin, but it's not very specific and I'm not getting any similar errors elsewhere. The site has been in production for months, and I've only just bought this plugin.

Any clues please?

I add Türkçe texts to a markdown field and save content then reload the page. while seopro addon is installed, the page doesn't render successfully.
and when I remove SEO pro, the page renders successfully.
Try yourself, add this text to About me page of default installation of statamic, save and reload page:

Serdar Ortaç (d. 16 Şubat 1970; İstanbul), Türk şarkıcı, söz yazarı ve besteci. Bazı müzik eleştirmenleri tarafından kendisinin Türk pop müziğinde bir dönemin standartlarını belirlediği kabul edildi ancak 2000'li yılların başından sonra ürettiği şarkıların birbirinin tekrarı olması gerekçesiyle olumsuz eleştirildi.[1][2]

text source: wikipedia

statamic: 2.10.4
seopro: 1.0.2
php: 7.2
server: nginx

console error:

I'm pretty sure, the sitemap should not contain collection entries which has a date in future.

It's not possible to properly schedule entries when google gets the hint of upcoming entries through the sitemap.

Problem/Motivation
SeoPro currently includes pages, entries and terms in the sitemap. This does not include routes directly rendering a template.

Proposed solution
Throw an event in Sitemap::pages() allowing modules to alter pages rendered in the sitemap. This event could be used to add, modify or remove pages.

I will submit a pull request if you think the proposed solution makes sense. :)

Hi,

First thanks for this plugin, I love it

The only one feature I miss, is to be able to edit values of SEO tab for each local of a page.
Actually all fields are disabled when I try to edit a locale that's not the default. (en here)

Thanks for your help!

Cheers 😃

Generating the metatags is a nice thing, but how can I access the SEO data individually? I have a custom Pinterest share button and want to pass the SEO title, description and image to the Pinterest share URL...

<a href="http://pinterest.com/pin/create/link/?url={{ current_url | urlencode }}&amp;media={{ image }}&amp;description={{ description | urlencode }}">Pin</a>

So the title and description fields have {{ company_name }} but the seo plugin is displaying it as empty. But if the same is used anywhere else on the page it works.

In section defaults, go into a collection, toggle enable to be off and save.

The toggle for enabled reverts back to on.

However, check the folder.yaml for the collocation and you will see seo: false.

So the setting is working, it just always shows as enabled in the CP.

FYI, works fine for taxonomies.

If I use a pipe | I think the YAML is interpreting it. I have to do '|' in order for it to take.