← Back to Multi-lingual SEO & Sitemap Support
Hi there, I'm relatively new to OctoberCMS and stumbled when following your documentation.
I've added the component to all my layouts as instructed, but I don't understand/can't find what this means:
"Then you should create a SEO register for every page in your theme. Fill the title, description, (optional) keywords and (optional) image in each language."
Can you give me a pointer please? I don't see any additional tabs on my pages where I might complete that information and I'm not sure what I'm missing.
Thanks in advance!
You should see a new option in your top menu, see this screenshot: https://octobercms.com/storage/app/uploads/public/5bf/66e/177/5bf66e177e315686511727.png Here is where you can create the SEO registers.
Maybe there's a better way to explain this point in the docs. "You can go to the SEO top menu option and create an SEO entry for each of your theme pages" sounds good?
It would be a lot more intuitive if there were a tab on the page itself, rather than have to exit to a totally different place and create a new entry.
If you're trying to encourage best practice by providing SEO info, forcing someone to double their workload isn't really ideal - but perhaps I misunderstood something (none of my existing pages were present in that section).
It would be a lot more intuitive if there were a tab on the page itself, rather than have to exit to a totally different place and create a new entry.
If you're trying to encourage best practice by providing SEO info, forcing someone to double their workload isn't really ideal - but perhaps I misunderstood something (none of my existing pages were present in that section).
Yes! you are correct, a new SEO tab should show up in pages, that would be ideal. In fact, there's another plugin that does exactly this (https://octobercms.com/plugin/renatio-seomanager), but it's not multilingual. The problem is that this type of multilingual extension of pages/models is not possible right now with the translation plugin, so we use this method. We expect to be able to add it as a tab in a not too distant future.
Anyway, but this is maybe just our use-case, we don't like to allow backend content-managers to modify CMS Pages. Having the hability to enter SEO content from another different place is useful in this situation.
Hi I have followed the documnetation but I am unable to get the og:image property to work any suggestions this dispays nothing "{% if seo.hasSeoPage %}
<meta name="title" content="{{ this.page.title }}" />
{% if this.page.keywords %}
<meta name="keywords" content="{{ this.page.keywords }}" />
{% endif %}
<meta property="og:title" content="{{ this.page.title }}" />
<meta property="og:description" content="{{ this.page.description }}" />
{% if this.page.seo_image %}
<meta property="og:image" content="{{ this.page.seo_image.getPath() }}" />
{% endif %}
{% endif %}where as this " {% if this.page.seo_image %}
{% endif %} " displays everything but the image content
Last updated
having problems getting any values to show up on blog post page using the default code
<title>{{ this.page.meta_title }}</title>
<meta name="description" content="{{ this.page.meta_description }}" />
<meta name="keywords" content="{{ this.page.meta_keywords }}" />
<meta name="title" content="{{ this.page.meta_title }}" />
<meta property="og:title" content="{{ this.page.meta_title }}" />
<meta property="og:description" content="{{ this.page.meta_description }}" />
{% if this.page.seo_image %}
<meta property="og:image" content="{{ this.page.seo_image.getPath() }}" />
{% endif %}but displays fine on cms pages any reason for this as only displays
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title></title>
<meta name="description" content="" />
<meta name="keywords" content="" />
<meta name="title" content="" />
<meta property="og:title" content="" />
<meta property="og:description" content="" />where as if add "{{ this.theme.website_name }} - {{ this.page.meta_title|default(this.page.title) }}" seems to work but can not find a way to get image value to work any help would be appreciated
After a bit os tinkering i have managed to get most of the iformation to work with the following
<title>{{ post.title|default(this.page.meta_title) }}</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="author" content="{{ post.user.first_name|default(this.theme.website_author)}}">
<meta name="description" content="{{ html_limit(post.summary, 140)|raw|default(this.page.meta_description) }}" />
<meta name="keywords" content="{{ this.page.meta_keywords }}" />
<meta name="title" content="{{ post.title|default(this.page.meta_title) }}" />
<meta name="generator" content="Drift-In {{ this.theme.website_name }}">
<meta property="og:title" content="{{ post.title|default(this.page.meta_title) }}" />
<meta property="og:description" content="{{ html_limit(post.summary, 140)|raw|default(this.page.meta_description) }}" />
<meta property="og:image" content="{% for image in post.featured_images %} {{image.path }} {% endfor %}{{this.page.seo_image.getPath() }}" />But I am struggling to find a method of displaying keywords for blog/post is there something I am missing as I see you say you have fixed the last bug or is there some themes this does not work on?
Figured out where I was going wrong should have read the documentaion on https://github.com/utopigstudio/octobercms-plugin-seo first rather than the ducmentation on https://octobercms.com/plugin/utopigs-seo site as it misses out a vital element and that is you need to add SeoModel component to the post or category pages which it misses out on octobercms pluging page of the documentation my bad but its been good working out how twig works to get different results
1-10 of 10