Stallion Responsive Theme version 8.4: added over 70 new color schemes! Stallion Responsive is not just a WordPress Theme that’s SEO friendly, it’s an entire WordPress SEO package of built-in plugins and SEO features taking WordPress to the next level in Post Panda SEO and Google performance metrics with advanced SEO measures to help take full advantage of the Google Hummingbird algorithm. Hummingbird is the Google search algorithm that understands human natural language patterns better than ever before: long tail keyword SERPs with a human touch and Stallion Responsive v8 includes multiple features to take advantage of Google: no other WordPress theme or SEO plugin has these Hummingbird features. Tested to WordPress Version 4.8.*. Note: It’s tested every day on […]
Continue Reading Stallion Responsive Theme
SEO of Social Media Profile Links
Wasn’t planning to make this change for the Stallion Responsive 8.1 update, but the irritation got the better of me :-)
The Stallion Responsive 8.0 social media profile links to Facebook, Google+, Twitter etc… that could be loaded on the top right or left side of the screen and within the author biography box (see the right hand side of this page and the author biography box) meant loading up to 10 external image links (to Facebook, Twitter etc…) to promote our social media profiles. If you showed the social media profile links on the top right and in the author biography box that’s up to 20 image links loading on every post!
Not ideal from an SEO point of view. I’d mitigated some of the SEO damage by incorporating the Stallion link cloaking script to these links, so at least Google didn’t read them as links, just saw the images. Still not ideal, but better.
Because of this it was best to limit the number of social media profiles to link to, that was until today :-)
Have rewrote the code (running now on this site). For those who have used the feature before the only thing you’ll notice is the social media profile image links no longer completely use the Stallion colour options, if there used to be a border around the image links it’s no longer shown (the theme colour I’m using didn’t have a border, so no change at all), everything else is as before.
What I’ve done is push the image links off the webpage that’s loaded and instead load them in an iFrame. If you’ve ever added a YouTube video to a WordPress posts it’s loaded in an iFrame, so using the same technique to load the social network profile image links.
This is the webpage the iFrame is loading for the social media profile links on the right hand side of the page.
https://stallion-theme.co.uk/wp-content/themes/stallion-responsive/social.php?author=1And this is for the author biography links:
https://stallion-theme.co.uk/wp-content/themes/stallion-responsive/social-bio.php?author=1iFrames basically load a separate webpage inside another webpage, like you see with a YouTube embedded video, the video is on a webpage hosted by YouTube not your website.
Google SEO wise the contents of an iFrame is for practical purposes invisible, links within an iFrame loaded page are not treated as links from the main webpage. The two pages above contain valid image links, Google can follow them and passSEO value, PageRank etc… but other than this comment the only reference to those two URLs are within an iFrame and iFrames don’t pass SEO link value: Google will probably index them now since it will follow a non-clickable links, but I’m not spending any link benefit to have those URLs indexed by Google.
Since there’s no good SEO reason to link to a Facebook profile from a website like this one, using an iFrame is ideal SEO wise.
Using an iFrame is also better Google performance wise. iFrames are loaded asynchronously, this means the browser doesn’t wait for the contents of the webpage within the iFrame to load while it’s loading the main webpage: if your website has ever stopped loading while it waited for a Twitter Tweet button to load (in Firefox the bottom info bar can indicate what isn’t loading fast with the “Waiting…” info) it’s because the browser wasn’t loading the Twitter button asynchronously, it’s loading the resources as it finds them in source, when one is delayed (a Twitter button loaded on Twitters servers) the browser waits for that resource to load or timeout……
As you can see I’m currently linking to Facebook, Google+, Twitter and Linkedin and since I have the links on both the right side and the author biography box I’m saving a browser from loading 4 images twice while the main text content etc… loads. Might not sound a lot, but every resource a webpage has to load takes time and Google is considering user experience more important, shaving off a few milliseconds might not be a big SEO deal today, but for Google 2015 it might be important.
Worst case scenario the user gets a better experience.
I’ve also modified the code to work better with multi author blogs, each author can set their own social media profile links. That’s why the two URLs above end in ?author=1 each author has a unique ID, main admin is 1. If this site had multiple authors (it doesn’t) ?author=2 would load a different set of profile links.
I want to move all the like type buttons to an iFrame as well, will be possible with some, but not sure about them all yet.
David
SEO of Social Media Profile Links
WordPress Performance SEO Update
The Stallion Responsive WordPress SEO Package version 8.1 is almost ready for release. Had it ready a week ago, but as I triple checked new features found performance issues I wasn’t happy with and fixed them, think I’m done now, so will test on some of my domains for another week and if no issues release the update.
Checkout the latest Google Pagespeed Insights Tools results for this domain: http://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fstallion-theme.co.uk%2F&tab=desktop
Mobile User Experience: 99/100
Mobile Speed: 88/100
Desktop Speed 95/100
Happy with these results because most of the issues are not on the site per se, they are related to social media like buttons. Main issue I have control over is “Eliminate render-blocking JavaScript and CSS in above-the-fold content”. It’s one css file (would be three without a minify plugin like W3 Total Cache) and though in theory could take out the important CSS rules and have them inline and load the not so important CSS files in the footer, it would be serious overkill for the gain.
It’s interesting on desktop I have 5 issues and loose 5 points, on mobile I have 6 issues (one additional image issue due to a resized image) and loose 12 points. Looks like on Desktop for each issue you loose one point, but on mobile it’s two points for each issue. Other than the image optimization issue, the pagespeed issues of Desktop and Mobile are identical. I suppose it makes sense with mobile devices bandwidth could be more limited meaning page speed is more important: twice as important according to Google :-)
Further improvements would mean turning off social media like buttons, think that would get me:
Mobile User Experience: 100/100
Mobile Speed: 96/100
Desktop Speed 99/100
Hmm, or maybe not look at which has no social buttons (archive part of site) http://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fstallion-theme.co.uk%2Fresponsive%2Fseo-tutorial%2F&tab=desktop
Mobile User Experience: 100/100
Mobile Speed: 91/100
Desktop Speed 97/100
Have the same two issues for mobile and Desktop which account for 9 points for mobile and 3 for desktop.
Makes even less sense now!!!
Far from an extensive list of improvements this week.
Stallion Photo Navigation Menu no longer uses javascript, the accordion style image menu used to require two javascript files (mootools js files) for the sliding effect, have rebuilt the feature using CSS styles to output an almost identical feature. See an example at http://wordpress-test2.xllx-inc.com/ it’s the photo menu near the top, only change is it’s a little wider and I removed a right border from the image bit.
The SEO performance benefit of the new code is no need to download two javascript files sitewide for a fancy image menu. Overall a saving of around 37KB no longer downloaded and the two calls to get the resources. Overall faster site speed. Also smoother sliding as device width decreases, before if you flipped a mobile phone to landscape view because the width was set using javascript it ideally needed a page refresh, now it doesn’t.
Had performance problems with Akismet 3 recently, they added the need to use Jquery for their SPAM honeypot! Also because I run over 100 domains my Akismet IDs (the free ones) kept getting cancelled, dealing with too much comment SPAM, so was a pain having to get new Akismet IDs and add them to dozens of domains! Not been running Akismet on this domain for about a month (just using Stallion), the site can see around 1,000 SPAM comments a day and Stallion is marking almost all of them SPAM (correctly, not had a false positive yet). With Stallion responsive 8.1 no longer need Akismet or any other comment SPAM plugins.
Stallion includes 5 SPAM protection measures:
1 – HTTP_REFERER check.
2 – Adds a nonce to stop comments being submitted remotely.
3 – Two SPAM HoneyPots, these are form fields real users can’t add content to, but bots tend to fill them tripping the SPAM honeypot. Thinking about adding the option for webmasters to set the name of the honeypot fields so even more likely not to be avoided by SPAM bots: spammers can avoid a honeypot if the spammer knows the hidden field name so they can set their bot not to add content to it. Giving webmaster the option to periodically rename them means if a bot avoids the pot it can be renamed, would be even better to rename it randomly (just had an idea :-)).
4 – SPAMMERS tend to post long URLs in the author URL box, if a URL is longer than X characters (you set X: default 60) it’s marked SPAM.
5 – 10 duplicate field checks, if a SPAM bot adds the same content to two fields it’s marked SPAM.
Had the last idea recently (not seen this SPAM blocking concept used before) because comment SPAM bots tend to copy the author URL field into the Stallion comment title field. When I see a URL as the comment title it’s always SPAM, so made sense to add a check for when content is used more than once in two or more comment form fields. Added 10 checks which covers everything possible, if the author URL is all that’s copied onto the main comment text it’s SPAM.
Should only leave manual SPAM comments, not much you can do to block them without using a service like Akismet that maintains a database of email addresses that’s had other users mark it as a SPAMMER. Problem with this approach is you’ll find in a niche like Internet marketing real commenter’s who aren’t SPAMMING are false positives.
WordPress core has a minor SEO issue with the reply to comment links: partially my fault, it was my suggestion that resulted in WordPress core removing the rel=”nofollow” attribute from the reply to comment links that resulted in this minor SEO issue :-)
The SEO issue is the reply to comment link URLs that are generated when a Reply to Comment link is clicked
are indexed by Google. There’s a correctly set canonical URL that let’s Google know the correct URL for indexing is
but you will still find in Google Webmaster Tools URLs listed with the above type of URL (under Crawl >> URL Parameters) and some indexed in Google. Pop the code below in a Google search:
site:https://stallion-theme.co.uk/ ?replytocom=Although it’s not causing SEO damage, Google is transferring the SEO benefit to the main URL it’s been irritating me, so have made a fix. Stallion for years has used form buttons for login links and comment author URL links for SEO reasons, have used the same SEO code for the Reply to Comment links. With Stallion 8.1 Google won’t ‘see’ the replytocom URL because it will be part of a form button and Google doesn’t treat them as links. Will take some time, but the currently indexed ?replytocom= links (Webmaster Tools says I have over 8,000 links with that parameter!) indexed will reduce since Google won’t have the links to reindex.
There’s also quite a big SEO benefit to this new feature, before the Reply to Comment links had anchor text “Reply to Comment” which isn’t very helpful SEO wise, now the button ‘links’ have a button with text “Reply to Comment”, but it’s not anchor text so doesn’t have any major SEO value: like everything on a page there’s an SEO impact, but now it’s insignificant.
While working on this code found I’d missed a rel=”nofollow” attribute (thought I removed them all). If you have comment posting only available to logged in users (so only those who register can comment) Google was getting a nofollow link to the register to comment link on every comment (not good!). Since it didn’t make sense to have a “Register to Reply” link on every comment removed the link completely leaving the one link where the comment form would be to register (that’s not nofollow): so users still have a route to register, just not dozens of links saying register to comment.
Added Pinterest verification option on the Stallion Promotions page and added a register any webmaster like service that uses a meta tag to verify. The Russian search engine Yandex for example uses a meta tag to verify, pop their meta tag in the Stallion “Full Verification Meta Tags” form and the meta tag will be added to the head of the home page only. Any service that uses a meta tag verify tag can be verified easily.
Been working on a lot of features I’ve not mentioned previously, so have fun when I release Stallion 8.1.
BTW been developing in WordPress 4 beta 2 (nightly cutting edge builds) and WordPress 3.9.1 which just updated to WordPress 3.9.2 and not had any issues, don’t see any issues when WordPress 4.0 is released, but you never know for sure until it’s actually released.
David
WordPress Performance SEO Update
Stallion Responsive WordPress SEO Package v8.1 Update
Have today (August 10th 2014) released Stallion Responsive 8.1, for current customers should be available as an update on your Dashboards.
Done really well for a release time frame, was aiming for the end of July and taking into account testing I’m pretty much on schedule: first time ever :-)
One feature bug, actually an issue with WordPress widgets. If you add new options to a widget WordPress doesn’t have an option to set defaults if the widget is already used. In this update I’ve added multiple new options to the “Stallion SEO Posts Widget” and the “Stallion SEO Recent Comments Widget” which means right after upgrading to Stallion 8.1 those two widgets are missing settings and don’t work correctly (widget output is blank).
It’s a very easy fix, go to “Appearance” >> “Widgets” and edit all instances of those two widgets you currently have on a sidebar. When the widget options drop down click the “Save” button at the bottom and the default options will be added. This isn’t an issue for new installs or adding another instance of the widgets, the defaults are set automatically when the widget is dragged and dropped. Bit of an oversight for WordPress core not to have a check option for if a widget has new options so defaults can be added automatically.
I’ve added several new options to those widgets, so check the defaults work with whatever you had before. You might have to increase the default numbers (set to 5) to match the number of posts you are loading. Really cool features, you can set how many of the links have thumbnails and excerpts now.
For those updating you can update the main parent theme under your dashboard, the free child theme has to be installed manually, this is because a child theme is for making modifications and if I added an auto update feature (I could) it would delete any modifications: AKA support nightmare….
Download the child theme zip file, unzip on your computer and use FTP to upload to /wp-content/themes/stallion-responsive-child/ making sure if you’ve made any modifications to the child theme you have a backup copy offline so you can add the modifications back in after update.
There’s no major changes to the child theme, there’s the latest version of the timthumb.php file and have included the Stallion mobile menu image for all the theme colours (will explain why below). So there’s no major code changes to the child theme, don’t NEED to update to 8.1 if you’ve made loads of mods to the 8.0 child theme.
Stallion Responsive 8.1 sees a major improvement in the Stallion Colour Scheme Creator feature, the 8.0 version required manually copying the CSS rules and the backup PHP code, in 8.1 it’s all automatic.
When you save a colour change two files are automatically created, they are saved in the child theme under
/wp-content/themes/stallion-responsive-child/colors/ – saves the css file
and
/wp-content/themes/stallion-responsive-child/mydefaults/css/ – saves the php backup file
This means Stallion will automatically find and use both those files without messing around with creating new CSS files or PHP files and uploading via FTP to use them.
Does mean you have to be a little more careful in saving your new colour schemes, if you edit a default colour scheme the CSS file is automatically saved to /wp-content/themes/stallion-responsive-child/colors/ and used by WordPress if you later choose to use that colour scheme. The original CSS files are NOT changed, they are still under /wp-content/themes/stallion-responsive/colors/ but WordPress will preferentially use the file from the child theme folder.
If you make a mess use FTP to go to
/wp-content/themes/stallion-responsive-child/colors/
and
/wp-content/themes/stallion-responsive-child/mydefaults/css/
and delete the relevant files for the colour scheme you edited and Stallion will again use the files from
/wp-content/themes/stallion-responsive/colors/
and
/wp-content/themes/stallion-responsive/mydefaults/css/
Can then start again.
If you do plan to make new colour schemes or edit current ones best to install the v8.1 child theme because the mobile menu images are now included in the child theme. If you don’t update to 8.1 you’ll have to manually copy the relevant mobile.png images from:
/wp-content/themes/stallion-responsive/colors/images/
to
/wp-content/themes/stallion-responsive-child/colors/images/
Lots on new features with Stallion Responsive 8.1, many related to performance, run your site through Google PageSpeed Insights Tool and compare to my results using Stallion Responsive 8.1 and W3 Total Cache for CSS minification etc…
http://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fstallion-theme.co.uk%2FFor those holding off buying at $100, please be aware the price is going up to $200 just as soon as I’ve sent out an email to all Talian 5 and Stallion WordPress SEO v7 customers letting them know Stallion Responsive 8.1 is available for $100. One week after the email is sent the price goes up and will not come back down in the near future, I’m also not offering any discounts at $200, it’s going to be a fixed $500 price period.
If you want my awesome SEO work which would be a bargain at $1,000, pay for it or use an inferior theme like Thesis or Genesis with Yoast WordPress SEO ROFLOL. Go checkout sites running Thesis and Genesis with the Google PageSpeed Insights Tool and also ask how a plugin like Yoast WordPress SEO can improve SEO performance by changing title tags?
David
Stallion Responsive WordPress SEO Package v8.1 Update
WordPress Comment SPAM
Found my first Stallion 8.1 bug in the new comment SPAM feature.
Stallion Responsive 8.1 comment SPAM filtering is so good since activating it had only two comments go to SPAM and one of them is due to a bug, rest dealt with before it was added to WordPress.
With Akismet would be at around 3,000 in the same period: stopped thousands of SPAM comments before being added to the database = big performance tick using Stallion Responsive.
To the bug.
When a logged in WordPress user has added their website URL on their profile page and the comment author URL is disabled (Stallion feature), Stallion will post the logged in authors comment URL. Like this comment will have a link to home where my author name is next to the avatar, but if you post a comment you can’t add a author URL, don’t want anyone posting comments for backlinks.
Added a new SPAM filter few days before releasing final Stallion 8.1 which when the author URL is disabled it checks if an author URL has been added and if it has adds it to SPAM. Looking at the core WordPress code I thought WordPress dealt with a logged in author URL in a different way to non logged in, apparently not.
Felt sure I’d tested this permutation and it didn’t trip the filter: logged in user, author website added to profile page, author URL turned off on the Stallion SEO options page. Apparently not as it trips the filter.
Will be adding a fix (was an easy fix) that I’ll upload to the zip files within the hour.
For anyone who has already updated it’s this file:
/wp-content/themes/stallion-responsive/plugins/stallion-stop-stupid-spambots.php
Near the bottom change:
<?php if (st_author_links() == '0') { #function str_remove_comment_fields($fields) { #unset($fields['url']); #return $fields; #} add_filter('comment_form_default_fields','str_remove_comment_fields'); function str_url_spamcheck2( $approved , $commentdata ) { return ( strlen( $commentdata['comment_author_url'] ) > 1 ) ? 'spam' : $approved; } add_filter( 'pre_comment_approved', 'str_url_spamcheck2', 99, 2 ); } ?>to
<?php if (st_author_links() == '0' && !is_user_logged_in()) { function str_remove_comment_fields($fields) { unset($fields['url']); return $fields; } add_filter('comment_form_default_fields','str_remove_comment_fields'); function str_url_spamcheck2( $approved , $commentdata ) { return ( strlen( $commentdata['comment_author_url'] ) > 1 ) ? 'spam' : $approved; } add_filter( 'pre_comment_approved', 'str_url_spamcheck2', 99, 2 ); } ?>Or upload the one file via FTP. Not going to change the version number for this small bug, so for those that updated will require the minor modification.
For those that understand code what this does is check if the Stallion hide author URL option is set (0 means off or no author URL field loads), followed by checking if the user is NOT logged in.
If user not logged in and Stallion is set to not show the author URL, remove the URL field.
Stallion has a custom URL field for, so this is a double check just in case if a real commenter manages to add a URL even if the comment field isn’t shown, this removes it.
The last bit adds a function that checks if the comment data includes the author URL field and if the content is above 1 character in length.
If a user is logged out they can’t add an author URL when Stallion hides the URL field, if they can somehow add a URL it’s almost certainly a SPAM bot directly hitting the core WordPress file /wp-comments-post.php (used for posting comments) so we can set those comments to SPAM.
I considered having this filter not allow the comment to be posted at all, but not 100% sure if real commenters can accidentally add a URL, so going with SPAM until I’m sure. If for the next update I’ve not seen real comments marked as SPAM I’ll filter these out completely like some of the other SPAM filters that throw out an error message to go back and change something.
David
Update: have uploaded a new Stallion Responsive 8.1 zip file. Realised as I fixed this bug the feature as a whole is going to filter trackbacks as well (I’ve never allowed trackbacks on a site and didn’t think to test them). I’m not going to add a fix for trackback URLs for this update since trackbacks are SEO damaging (should never allow trackbacks). Will figure out a fix for trackbacks next update.
WordPress Comment SPAM
I Want To Buy SEO Package
Hi,
I found your website by searching Google with “seo tutorial” – I am interested to buy – can you please guide me ?
Thanks 343
Buy WordPress SEO Package
Not doing too bad for the SEO Tutorial SERP.
I’m glad to hear you want to buy Stallion.
You can buy the Stallion Responsive WordPress SEO Package via PayPal by clicking the “Buy Stallion Responsive” button on the left menu.
Don’t wait too long, the price is going up soon.
Installation instructions and tutorials can be found on the main Stallion Responsive page.
David
Buy WordPress SEO Package
Stallion Responsive 8.1 Update
Hello, I have Stallion 8.0 installed on my blog.
And I got a mail from which I got to know that the current version is 8.1.
How to upgrade it in the lest troublesome way?
How to Update to Stallion Responsive 8.1
Easiest way to update from Stallion Responsive 8.0 to 8.1 is using the automated update.
“Dashboard” >> “Updates” – tick “Stallion Responsive” update and “Update Themes”.
To update the Stallion Responsive Child Theme, download latest zip file from the Child Theme page. Unzip and upload it over the current files (at “/wp-content/themes/stallion-responsive-child/”) using FTP.
FTP will also work for the main theme files if you prefer to use FTP for both.
Your Stallion Responsive 8.0 settings will remain intact. One exception, I added new options to the Stallion SEO Posts widget (widget that makes Popular Posts etc…) and there’s no way to auto update new widget options.
Easy to sort, after the update go to “Appearance” >> “Widgets” and for any Stallion SEO Posts widgets just resave them (click Save). This will add the new defaults.
After that go through the options pages to see if any of the new 8.1 features are of interest, by default I tend to set new features to off.
The above assumes you haven’t modified the main theme files or the child theme files, if you have you will need to ideally modify the new Stallion Responsive 8.1 files with your modifications or at least compare the files you’ve changed to the new to see if I made any significant changes.
Always put your modifications in the child theme folder, makes updates easier.
David
How to Update to Stallion Responsive 8.1
Your Themes are all up to Date
I tried to update from the dashboard. But I had an information there:
“Themes
Your themes are all up to date.”
WordPress Update check
Since users sites have to contact my server to check if there’s an update available, in my log files I can track down all domains that have checked if there’s an update and when that check is made it lists the Stallion Responsive version.
Can also search the logs for a specific Stallion Responsive ID as well, so can manually compare the two results.
Since you have your ID running on multiple domains I don’t know which one is the issue domain.
I can see multiple domains you own are contacting the update check feature (but not all have), an example is your Ipad Guide site which I assume is still running v8.0 (last update check it was 8.0).
Is there an update available for that domain? There should be.
If you run all your domains with the same host and not all are showing an update yet could be WordPress hasn’t checked for an update while you are logged in.
The feature is hooked into the WordPress update check with an only run when a user is logged in. Original script would check much more frequent which isn’t good for my server so changed it to only check when a user is logged in to reduce the load on my server.
I thought WordPress automatically checks for updates when a user is logged, after some checking I’m not sure that’s the case. To force a Stallion Responsive update check go to:
“Dashboard” > “Updates” : click “Check Again”
That will force WordPress to check for all updates and as you are logged in also check my server for a Stallion Responsive update.
Spent half an hour testing the feature and I found simply going to the updates page ran an update check as long as 1 minute had passed since the last WordPress update check. So don’t know why you haven’t seen an update after simply visiting the Updates page.
David
WordPress Update check
SEO Options Not Saving
Hi David,
Im setting up stallion on a test site and I have registered the theme and it says running in full mode.
When I click the
Use My Default Settings File SEO Version : stallion_defaults_seo.php and save
it keeps restting to
Use Current Settings
I have done this a dozen times and it doesnt seem to be saving and showing changes.
Thanks for your reply
Apols for the basic question :-)
Blessings!
Carl :-)
SEO Options Not Saving
WordPress SEO Options
Had this same question by email a week or so ago.
That’s what it should do, it’s importing the best WordPress SEO options once, you don’t need to keep reimporting the same SEO options.
The option you set loads whatever options are in stallion_defaults_seo.php completely over writing what is currently in the WordPress database.
That’s all the files do, they quickly overwrite ALL the current options to what’s in the file, after that what’s in the WP database (the SEO options you just imported) are used by Stallion/WordPress not the options in the file (you could delete the file, not needed).
If the setting remained on
“Use My Default Settings File SEO Version : stallion_defaults_seo.php”
Everytime you saved the main Stallion options page everything would be again read from the stallion_defaults_seo.php file overwriting any settings you further modified manually (the normal way clicking options on/off etc…) and you’d be complaining all your manual changes are being reset :-)
The idea is you can add your preferred Stallion Responsive settings (your AdSense pub number, Twitter name etc…) to one or more of the files for all your domains, load them and modify the options further the normal way.
The options added via stallion_defaults_seo.php after you click save will only be changed if you manually change them (clicking an option on/off etc… on an options page) or you change the contents of the file and you run the “Use My Default Settings File SEO Version : stallion_defaults_seo.php” again.
This way if you own 20 domains you can create one stallion_defaults_seo.php file for them all, import the settings to each domain and make minor options changes for each domain: each domain will need unique Google Analytics code for example (assuming you use Google Analytics) or a different colour scheme, but the main options you’ll probably want the same.
Once you have a set of basic options you like it saves a lot of time (that’s why I added the feature, I own 100+ domains: few clicks I’m done), run the file, change a few specific options for each domain: I manually add Google Analytics for each domain, set a different colour scheme, but don’t have to change 99% of Stallion Responsive options from the SEO defaults after running the option.
I use Stallion Responsive on a lot of sites, so when I find myself spending hours doing the same thing over and over again for different domains I try to create a solution to automate.
So it’s working as it should.
David
WordPress SEO Options
SEO Options Saved
Thanks for your feedback,
I think i worked it out coreectly.
I did this:
I copied the stallion_defaults_seo.php code to a custom file number 1 and then put that in the child theme and selected that and saved. It seems to be saving settings ok. Prior to that there were no settings in the child theme.
Blessings!
Carl :-)