Jump to content

MarkupSEO - The all-in-one SEO solution for ProcessWire.


Recommended Posts

Maybe it can steal an idea from Ryans table field - have its own table.

Or, it could also have its own PW page structure, effectively a "related" page to the current page, that is stored under admin somewhere in the same way repeaters are.

Though I think a single table might be more efficient, query wise.

However, just to change my mind again, the other day I put on my own site drop downs for Open Graph page type (article and so on) and the same for twitter. I did those with a page field so I have started with the most common five or six, but can add more on the fly as normal with a page-field. Useful functionality for this kind of thing.

So, maybe a mix! :)

  • Like 1
Link to post
Share on other sites

Though I think a single table might be more efficient, query wise.

I'm implementing a custom field type based on Ryan's Event field type that uses a custom table for storage.

I have compared performance to other methods like using a pages field. And the custom table field is much much faster, both when saving and querying values. So I'd recommend going with the custom table field following Ryan's Event field type module.

  • Like 1
Link to post
Share on other sites

As @lisandi said. 

An example:

Your page's title is "About".

You use "<h2>$page->title</h2>" in your template but you want to have a different description on Google results like "Learn more about the team." 

Just use the title field to archive that.

Link to post
Share on other sites

   What an awesome module, the features in it are perfect. One thing I am noticing though is that the module seems to be a bit finnicky with images that are limited to 1 not on the current page, as the image preview function appears to call first() on the image field regardless to it's existance on the page.

Error: Call to a member function first() on a non-object (line 326 of home/swflemin/public_html/dg/site/modules/MarkupSEO/MarkupSEO.module) 

if($this->imageSmart && $pageDataDefault['image'] == '' && @$this->page->get(implode('|', $this->imageSmart))->first()->url != '') $mixedData['image'] = $this->page->get(implode('|', $this->imageSmart))->first()->url;

Looks to be the culpret. Could I get a hand modding this here?

Link to post
Share on other sites

Great Piece.

I've done something like that with textfields and FieldsetTab. But a Out of the Box Solution is quite nice.

A client had requested once, a SEO traffic light, which checks different basic things like the Title, Image Description, Keyword Density, List of the actual keywords in the existing text etc.

In my opinion you can achieve this as well with a small SEO cheatsheet and a bit brainpower. But on the other hand, it might be helpful for user, with less Web/Seo Knowledge.

Would something like that be possible? Or is something like that already in your mind?

  • Like 1
Link to post
Share on other sites

I'm very excited about this module. Thanks galore Nico.  I need all the help I can get w/ SEO. This is a boon.
 
From my reading, I agree with a prior comment that the automatic rendering should not be at the bottom of <head>, so I set the method to "manual", and tried to use
 

<?php echo wire('page')->seo->render; ?>

 long-hand toward the top of head.  It smoked!
 
In your ready() function,

$this->method == 'auto'  

should not be a condition for initializing the front-end hooks.

Thanks. 

Link to post
Share on other sites

Thanks for feedback! How would you initialize the hooks?


@ole: If I find the time I will update my to-do list and add some more features. I think I need to restructure it first to make it more flexible again.

  • Like 1
Link to post
Share on other sites

In my copy, this is what it looks like now. I don't know whether I'm missing something. I haven't created a module w/ hooks like this yet.

public function ready() {
		// backend hooks
		$editedPage = wire('pages')->get($this->config->input->get->id);
		if(@$this->page->process == 'ProcessPageEdit' && !in_array((string)$editedPage->template, $this->excludedTemplates)) {
			$this->addHookAfter("ProcessPageEdit::buildFormContent", $this, 'addSEOTab');
			$this->addHookBefore("ProcessPageEdit::execute", $this, 'saveSEOTab');
		}
		
		// frontend hooks
		
		// if($this->method == 'auto' && $this->page->template != 'admin') {
		if($this->page->template != 'admin') {
			$this->addHookProperty("Page::seo", $this, 'hookFrontendPage');
			$this->addHookProperty("Config::seo", $this, 'hookFrontendConfig');
		}
	}

Actually, why are you even explicitly skipping the 'admin' template if you have a mechanism for excluding templates in place and the 'admin' one is added by default?

Then, maybe, this is it:  It works, not stress-tested...

// frontend hooks

if (!in_array((string)$this->page->template, $this->excludedTemplates))  {
    $this->addHookProperty("Page::seo", $this, 'hookFrontendPage');
    $this->addHookProperty("Config::seo", $this, 'hookFrontendConfig');
}
?
Link to post
Share on other sites

Well I'm stumped, I can't seem to figure out how to get this to work with my site's images as many are set to one, and many pages don't contain the images that are referred to in the module. Looks like I'll be waiting for the next release :).

Link to post
Share on other sites

Hi Nico,

great idea, this spares quite some time to set this up individually.

One question about "Keywords". Do you mean the Keywords Meta Tags?

Google says they don't use it any more: 

http://www.mattcutts.com/blog/keywords-meta-tag-in-web-search/

Some of our clients had a wrong idea of SEO when spending a lot of time end efforts with littering the SEO keywords meta tag with all sorts of words, instead of using their energy on other SEO more relevant topics, like a carefully chosen title and a good summary. So we stopped offering that field. :-)

This is (in German) what Meta Tags Google uses:

http://support.google.com/webmasters/bin/answer.py?hl=de&answer=79812

EDIT:

A given "Focus Keyword" for a page might be a good source for your planned suggestion tool, the WP Plugin SEO YOAST seems to use it that way.

Edited by ceberlin
Link to post
Share on other sites

If you try to get clever and stuff your site with a lot of keywords this can even lead to search enigines penalizing your site score. In general i think it's best to focus on good titles, descriptions and content and don't use keywords.

Link to post
Share on other sites

Keywords still play a role but they need to be related to what you write in the text on the frontpage itself. This is quite important as otherwise you getpenelaized. But it means also that search engines still use the field and there are more search engines than only Google!

Link to post
Share on other sites

I personally won't waste to much time in keywords but from a business point of view "keywords" is itself such a manifested keyword for selling a website as a SEO website! And alone because of that I would leave the field just where it is inside the SEO Tool and the website. Let the customers fill it up like doctors give them some placebos and they will buy your sites ;-) and ideas!

Link to post
Share on other sites

As far as I am aware, Google definitely don't use Meta Keywords, Bing definitely doesn't and it looks like Yahoo don't either.

Keywords are also a lovely way of telling your clients' competitors what words are important to your client. 

I use them all the time - reading them from the competitor's website. :)

  • Like 3
Link to post
Share on other sites

Google hasn't used Keywords as a ranking metric since 2009-ish. Here's the offical post from Google.

I think the keywords field should stay. Clients are hard-wired into believing that Keywords matter because they did for so long.

Not having a Keywords field could negatively impact first impressions from some clients.

As someone else mentioned, other Search Engines might have their own policies re. keywords. I'm not an SEO professional.

For anyone wondering where the focus should be, the two most important ranking factors used by Google are:

  1. Quality incoming links from relevant sites. Quality is the key here and 3rd party sites themselves must have a good reputation.
  2. Relevant, quality content that is updated and shareable. 

I think in total  there are thought to be around 200 "signals" which Google ultimatelty uses to determine ranking.

Any SEO pros on here to confirm?

Link to post
Share on other sites

Matt Cutts about WordPress and SEO - worth watching!



Listen carefully as you will here "keywords" ....
- don't mix that tool up with seoiq.de (Trittbrett Fahrer)

keywords in meta data are not the same like "on-page keywords"!!! The later is still quite important, even with Google.

200 Faktors
http://www.entrepreneur.com/article/226884

Daily Google is changing their algorithms so change your way of doing SEO at the same rate and you will be on the top of the pop perhaps!
Goos SEO means at first place high quality content - and this content in on the visible site of all web pages and pages need to perform very good - speed!
Test your sites in http://gtmetrix.com

 
  • Like 1
Link to post
Share on other sites

As far as I am aware, Google definitely don't use Meta Keywords, Bing definitely doesn't and it looks like Yahoo don't either.

Out of interest, do you have any details on the Bing and Yahoo parts? Google is obvious, but as far as I can tell, Bing and Yahoo still use keywords, though they're not exactly important ranking factors (quite the opposite, really -- they seem to have much less weight than regular body copy).

Also, for anyone targeting the Russian or Chinese markets, it should be noted that Yandex specifically suggests using meta keywords (they're not revealing how important these are as ranking factors though) and according to some sources Baidu considers meta keywords "very important" (though keyword stuffing is a major negative signal there too).

  • Like 3
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
×
×
  • Create New...