Jump to content
Nico Knoll

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

Recommended Posts

@teppo: To be honest: I didn't think about that... Maybe I'm switching to create real fields so multilanguage will be easier, too. Have to think about it later today :)

  • Like 3

Share this post


Link to post
Share on other sites

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

Share this post


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

Share this post


Link to post
Share on other sites

Hi Nico, nice module, i was going to build it myself, but you were quicker :)

But why does it have a own title field? As every page already has a title why double it?

Share this post


Link to post
Share on other sites

@jmartsch The title field is actually good as you can use it as a browser title field which can differ from the page title or an ulr pathsegment etc.

 

  • Like 5

Share this post


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.

Share this post


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?

Share this post


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

Share this post


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. 

Share this post


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

Share this post


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');
}
?

Share this post


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 :).

Share this post


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

Share this post


Link to post
Share on other sites

Well yeah it creates the keywords field. I've never been that deep in SEO so I thought this field would still be relevant. :)

Thanks for the tip with the Focus Keyword !

Share this post


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.

Share this post


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!

Share this post


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!

Share this post


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

Share this post


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?

Share this post


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

Share this post


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

Share this post


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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...