From 7f8a81d1333c8d837f422535c480d804a8dc83eb Mon Sep 17 00:00:00 2001 From: janhenckens Date: Thu, 11 Apr 2024 11:52:01 +0000 Subject: [PATCH] deploy: 66cfcd405d1f297eefb834f40af686061bc0ebc5 --- 404.html | 2 +- field.html | 2 +- general.html | 2 +- hashmap.json | 2 +- index.html | 2 +- notfound.html | 2 +- redirects.html | 2 +- robots.html | 2 +- schema.html | 2 +- settings.html | 2 +- sitemap.html | 2 +- templating.html | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/404.html b/404.html index 34938ed..46db41e 100644 --- a/404.html +++ b/404.html @@ -17,7 +17,7 @@
SEO Fields

Appearance

404

PAGE NOT FOUND

But if you don't change your direction, and if you keep looking, you may end up where you are heading.
Take me home
- + \ No newline at end of file diff --git a/field.html b/field.html index e60a7ce..e34bb29 100644 --- a/field.html +++ b/field.html @@ -20,7 +20,7 @@
SEO Fields

Appearance

Brought to you by:

Field ​

Important

The plugin assumes that the handle of the SEO Fields field will be simply: seo. If it can't find that field, it won't output anything.

If you use a different handle for your field, simply copy this file to the config directory of your project and change the fieldhandle to your own.

Here's what the field looks like the CP:

Field settings ​

In the field settings you can enable or disable the following:

  • Show the general tab
  • Show the facebook tab
  • Show the twitter tab

Under the advanced options you can:

  • Enable the option to hide the site title
  • Enable the option to hide the site title
- + \ No newline at end of file diff --git a/general.html b/general.html index 8c13a26..6bfc6b5 100644 --- a/general.html +++ b/general.html @@ -20,7 +20,7 @@
SEO Fields

Appearance

Brought to you by:

Usage ​

1.Setting defaults ​

After installing the plugin, you'll want to set defaults for your site. You can set:

  • a default site title (that will be added after the entry's title
  • a title seperator to go between to entry title and the site title
  • a default meta image.

If you have multiple sites in your install, you can specify different defaults for each site.

2. The field ​

Next up, you create an SEO Fields field and add it to your section's layout. More about the field and it's options can be found here.

3. Rendering ​

Add {% hook 'seo-fields' %} to your layout.

- + \ No newline at end of file diff --git a/hashmap.json b/hashmap.json index d37f771..e7f7afb 100644 --- a/hashmap.json +++ b/hashmap.json @@ -1 +1 @@ -{"schema.md":"bWDOHcw_","robots.md":"aGdPGvMq","notfound.md":"2C3mbEmP","index.md":"sxjbx6e7","redirects.md":"7dJ_S3wv","templating.md":"-IXD5ZfE","settings.md":"M_LBrEG1","field.md":"vU2OPlYj","general.md":"RcQnbUpO","sitemap.md":"2CY_pmxA"} +{"notfound.md":"2C3mbEmP","redirects.md":"7dJ_S3wv","index.md":"sxjbx6e7","schema.md":"bWDOHcw_","field.md":"vU2OPlYj","settings.md":"M_LBrEG1","templating.md":"-IXD5ZfE","robots.md":"aGdPGvMq","general.md":"RcQnbUpO","sitemap.md":"2CY_pmxA"} diff --git a/index.html b/index.html index 1872145..856c213 100644 --- a/index.html +++ b/index.html @@ -27,7 +27,7 @@ # tell Craft to install the plugin ./craft install/plugin seo-fields

Support & issues ​

Having an issue with the plugin or would you like to see something added, do report it here.

If you need help setting things up or you want to get in touch privately, get in touch.

Brought to you by Studio Espresso ☕️

- + \ No newline at end of file diff --git a/notfound.html b/notfound.html index 2ff26e2..d53655b 100644 --- a/notfound.html +++ b/notfound.html @@ -20,7 +20,7 @@
SEO Fields

Appearance

Brought to you by:

404 tracking ​

The plugin will keep track of visits and requests that resulted in a 404 (or "page not found") response.

These are tracked per site, with the number of times the specific url was visited (hits), when it was last visited - and show wether the "page not found" has a related redirect.

If there is no redirect linked to the url, you can create it from the overview by clicking the plus icon.

- + \ No newline at end of file diff --git a/redirects.html b/redirects.html index 531e9dd..26f4887 100644 --- a/redirects.html +++ b/redirects.html @@ -20,7 +20,7 @@
SEO Fields

Appearance

Brought to you by:

Redirects ​

You can redirect legacy urls, to make sure you don't lose SEO value when migrating/restructuring your website. Another use for this is a short urls that are easier to read or print, should you have need for those.

Important

These redirects will only work if there is no live page in the CMS with the same url. Otherwise that page will be shown first.

Redirect options/parameters ​

Old pattern or URL to redirect

This can be the full URL (with the domain) or just the URI (without the domain)

Which part of the URL should be matched

Options here are:

  • path or uri only
  • path or uri only without any query parameters
  • the full url

URL to redirect to

This has to be a a full url, not a relative one.

Match type

  • Exact match
  • Regex match

Match Type

  • 301 (permanent redirect)
  • 302 (temporary redirect)
- + \ No newline at end of file diff --git a/robots.html b/robots.html index 4eb257c..c1d5e17 100644 --- a/robots.html +++ b/robots.html @@ -20,7 +20,7 @@
SEO Fields

Appearance

Brought to you by:

Robots.txt ​

Default ​

When you install the plugin, it enabled the robots.txt by default, using this template.

Based on the environment you've set in your site's .env file, it will only allow indexing on live or production environments and block indexing on all others.

You can modify the template with your own enviroments, conditions and settings in the CP.

WARNING

Note that this will not stop Google from indexing your staging/dev site if and when someone else has a link to it. Always add another level of authentication to make sure Google can't index it.

Multisite ​

By default, each site in your Craft install will get the same robots.txt. If you need the option to change these per site, you can add "robotsPerSite" => true to config/seo-fields.php.

With that set, refresh the robots settings page and you'll see a sites dropdown at the top so you can switch sites and save a robots.txt for each.

- + \ No newline at end of file diff --git a/schema.html b/schema.html index 05431b1..1527aa7 100644 --- a/schema.html +++ b/schema.html @@ -29,7 +29,7 @@ .name("Studio Espresso") .email("info@studioespresso.co") |raw }}

Add your own types through settings ​

Out of the box, you can set a section to one of the following types:

You can extend this list by setting the schemaOptions attribute in the seo-fields.php settings file. You can find the syntax here

- + \ No newline at end of file diff --git a/settings.html b/settings.html index 9a3cabf..bca806b 100644 --- a/settings.html +++ b/settings.html @@ -23,7 +23,7 @@
SEO Fields

Appearance

Brought to you by:

Plugin settings ​

The following options can be set by copying this file to your project's config directory, and renaming it to seo-fields.php.

pluginLabel ​

How the plugin is labelled in the CP's sidebar, defaults to SEO

titleSeperator ​

Defaults to -

robotsPerSite ​

Whether robots.txt should be set per site, defautls to false

sitemapPerSite ​

Whether sitemap settings should be set per site, defautls to false

fieldHandle ​

This is the handle your SEO Fields - field has, defaults to seo but make sure to change this setting should your field be named differently.

notFoundLimit ​

The maximum number of "not found" or 404 items to track, defaults to 10000.

schemaOptions ​

Additional options to be listed in the Schema options per section. This take an array of :

  • the class of the Schema object (base on spatie/schema-org)
  • the label you want it be listed as

For example:

php
    "schemaOptions" => [
         get_class(\Spatie\SchemaOrg\Schema::recipe()) => 'Recipe'
     ],
- + \ No newline at end of file diff --git a/sitemap.html b/sitemap.html index 1c5cd61..bf79e30 100644 --- a/sitemap.html +++ b/sitemap.html @@ -20,7 +20,7 @@
SEO Fields

Appearance

Brought to you by:

Sitemap.xml ​

The sitemap includes support for Craft entries, categories and Commerce Products.

Support for custom urls and for registeren custom urls in code will be added in future release.

Multisite ​

By default, each site in your Craft install will get the same sitemap.xml, depending on wether the sections you've enabled in the sitemap are enabled for that site and when the section has entries that are enabled for that site. If you need the option to change enable/disable section in the sitemap per site, you can add sitemapPerSite => true to config/seo-fields.php.

With that set, refresh the Sitemap settings page and you'll see a sites dropdown at the top so you can switch sites and save a sitemap for each.

- + \ No newline at end of file diff --git a/templating.html b/templating.html index 107eeca..5b835c2 100644 --- a/templating.html +++ b/templating.html @@ -35,7 +35,7 @@ ]); } ); - + \ No newline at end of file