Guest Posts or User Submitted Posts are content written by another author not working for the site in which the content is being displayed on. UltimateSEO has a very easy guest post system and its free. Content submitted to our site may be syndicated on as many as 300 other sites that we maintain or are affiliated with. That can potential deliver you hundreds of backlinks from multiple domains. We offer this feature free of charge at this time, but may charge in the future. Why is it free when other sites charge? Its because we want good content and diverse opinions. So please ensure your post is original, timely, accurate and fresh.
Guest Posting is a win win scenario for us and you and your site. You can write an original article and we’ll post it if it is about SEO or SEM in general. Specific niche SEO topics are also welcome. Writers can include backlinks of relevant in their posts. We’d like to recommend no more than one link per 250 words. If there is an issue we’ll let you know. We also ask the your post include an image or an image per 500 words. So .in a 2000 word SEO post we’d like to see no more than 8 links and we would like to see about 4 images.
Ultimate SEO reserves the right to remove or edit posts on our site. We will also provide credit to content creators who retain ownership of their content but license the display of that content to use by using this form.
To submit your own guest post visit our submission page. Approved Guest Posts also appear among the site’s regular articles.
In PBNs 2019 Part 1 we discussed some logistics of organization on a high level concerning Cloudflare, Spreadsheets and above all randomness. In this the second part of our private blog network series we’ll focus on expired domains and the assessing of their value.
First, we will look at Domain Authority but before we do lets note Domain Authority in and of itself is worthless. It IS NOT used by Google. It is made by a company called Moz and it is their best guest how Google interrupts the content on a site based on a lot of factors but not all the factors and not in the same ratio. Why do we use it then? Google doesn’t have to tell us their formula for ranking a site in their results…in fact to do so would likely be a disservice to everyone involved. So based on observation and conjecture Moz provides us with an imperfect rating called Domain Authority. It is though in the end a made up number that is flawed. It was so flawed that DA 2.0 came out in March 2019 where many sites saw their rating plummet. Search results didn’t change … why would they when they are not connected to DA. Now thats out of the way…
We should start with https://expireddomains.net its a good site that has aggregated the domains being deleted from multiple registrars and it provides some base metrics that we can use to qualify domains for a closer look. There are millions of deleted domain names and we need someway to filter them down to something you can work with.
Why do we care about expired domains? Your PBN is attempting to mlmic organically earned backlinks. In the real world backlinks would likely come from sites that have their own backlink profiles and no two organic sites would likely have the same backlink profile. Buying a new domain name will come with 0 backlinks. Buying a used one will likely include some backlinks therefore giving your PBN its power. Think of these like telephone numbers…and you want someone to call you…you wont want to use the old number of someone who didn’t have any friends, but if you get a popular person’s old number then your phone is more likely to ring. Sure they are after the former owner ( or site in our case ) but if you can answer their questions and keep them happy they may keep calling. Same with expired domains.
Another site that focuses on expired domains is domcop.com. They are expensive and I’ve never used them because I can do all the work it does pretty swiftly and save the 100 dollars a month. Sure they have a cheaper plan but you cant do anything with it. Access to the expired section and archived section isn’t included …. making it relatively worthless. Back to expireddomains.net its free. Once we log in we can choose filters to sort down to the domains we want. Some of the filters I always put into play are:
Search and gain these results….
Now most of these values are worthless to me. They are cached results usually and not exactly accurate. SO I use the clip board icon to export the top 200 sites that made it through our filters. I sort these results though first by Domain Pop or DP in the graph. Use the clip board to export just the domain names to your clip board.
With these export names in order of domain pop I paste the results into a speed-sheet for safe keeping. And then I use a program called Domain Detailer. You can download it … its an application on PC. You can buy credits and each domain name looked up takes a credit. But you get a ton for your money. Ive probably spent 80 bucks on these credits and looked up over a hundred thousand domains in this tool. The metrics reported are more accurate than expireddomains.net metrics.
From Domain Detailer I paste the domain names I have selected and click “Add From Text Box” with credits the program will build you a spreadsheet with metrics that should be semi self explanatory. The metrics I focus on are Moz DA, Majestic Domains, Majestic TF and the categories. Backlinks are often off and its good that we have two sources … Moz and Majestics counts … if either has some I believe the higher one.
When I find a domain that has a mix of these metrics that seems above the group I move to the final phase.
I open SEMRush.com and search that domain name and verify that the domain pop is as good as I expected. I then check the anchor text and if the anchor text is consistent with the keywords I’d like to be pulling in I then say … its time to buy.
Remember to use a registrar that offers free private registration and shop around they are not all the same price.
We’ll talk soon about PBNs and the onsite things that you’ll need to consider when building the site up. You also may decide that you just want to help a specific site out and skip building a PBN site and 301 redirect all backlinks to the main domain…we’ll cover that as well in Part 3.
Ultimate SEO has gotten a little more ultimate. We continuing to offer our SEO information and topical articles and plan to expand into indepth discussions of stuff at the most minute details. Great for those of us who love metrics and but our metrics are only as good as the tools we can access. SEO tools are plentiful and almost all are expensive. The best tools focus on one aspect of SEO and do that well but effective SEO campaigns are holistic and can’t neglect other foundational tool categories. Having the best backlink tool won’t make the best SEO Site Audit. It takes multple tools, often overlapping and many cost hundreds of dollars a month. Thats why we’re launching UltimateSEO.net
SEO Tools are abundant but hard to find interestingly enough. At Ultimate SEO We’re offering more than one scan tool for page auditing. In the image below there is a scan auditing tool in the blue and yellow header and a separate unrelated scan auditing tool on the page. We encourage you to use both. Additionally from the Tools drop down you can take advantage of a dozen more SEO tools. We’ll work to continue to expand the sites tools and we will NOT charge for these tools.
In addition to these tools SEO Panel is an open source tool that will allow users to track metrics and issues over the course of months and years allowing sites to see trends. SEO Panel is also FREE but it does require registration at THAT site. SEO Panel is available at https://panel.ultimateSEO.org
CSV File Merger
Keyword List Multiplier
Structured Data Tool
Analytics Spam Tool
Bulk URL Checker
RSS Feed Creator
What’s My SEO Score (Page Auditor #3)
We also have an in-depth SEO tool available to our listers and visitors.
SEO Articles and case studies will be published and pieced together to create guides specific to topics of interest.
Forums and discussions between fellow SEO professionals are available and hosted at the site.
SEO Support Desk allows registered users to enter a support request .
Thanks for checking in with Ultimate SEO, this site is a side project as my client’s sites are the main one. This means I may often have edits and unfinished elements to circle back too. I encourage you to feel free to let me how this site could be better using the contact form.
I’ve heard things come in threes so curious whats next because 2 big updates this week are out. Now unfortunately the one that matters is unlikely to gain as much attention as the one that doesn’t mean anything. So lets begin on what folks are focused on…something that means nothing.
Moz redid their Domain Authoritycalculations and the implications are HUGE for those who workat Moz. If you don’t workthere then its not a big deal. Domain Authorityis like a fake credit score. Your bank will likely use your FICA score but no one can release your FICA score to you but FICA. To solve this banks and other organizations created their own scoring systems that attempted to mimic your FICA score that they can give out to you on credit monitoring sites. These numbers though aren’t really that important as they are guesses to what your FICA score should be…VantageScore for instance gives a person a score based on their credit history thats also 3 digits but it isn’t a FICA score. If you bank uses FICA scores who cares what your score is at VantageScore.
Moz made up Domain Authorityand Google doesn’t use it. So a change to calculating Domain Authorityfrom Moz does not mean a change in search engine ranking. Domain Authority is useful to you because it’s an educated guess as to what Google thinks just like Citation and Trust Flow are guesses by Majestic.
I don’t know about everyone else but the new calculations vastly changed the impression some would have of several domains I operate. Here are some examples:
But again, Domain Authority has value when used among multiple other metrics geared at assessing a site’s rank ability.
Its out and you can now run your site on it if you’re using Cpanel/WHM servers. Im focused on Cpanel because its highly popular …. unless you use Wix or Shopify which use propreietary server management software that isn’t an industry standard. Now, likely you don’t even use 7.2 as many sites still operate on PHP5.6. BUT here are the advantages of 7.3
Now its relevant to SEObecause WordPressruns on PHP and WordPressis an SEOfavorite. While new features are great and PHP 7 has proven much faster than PHP 6 this newest update may require some caution. PHP 7.3 Issue With WordPress 5
We have some testing done by others that note”
We wanted to test whether PHP 7.3 was performing better than PHP 7.2, and therefore bypassed the reverse proxy and ran tests directly against the backend web server running the PHP, effectively bypassing all caching. The tests were run from the server to eliminate network bias.
We used as the testing tool, running 3 000 requests with a concurrency of 1000, with keep alive enabled. ….
We did a few more compiles of PHP 7.3, and tested benchmarked those. We also did benchmarks on all major versions from 5.6 and up. See the results in the table below.
|Req/s||PHP 5.6||PHP 7.0||PHP 7.1||PHP 7.2||PHP 7.3||PHP 7.3 v2||PHP 7.3 v3|
We ran this test 3 times on PHP 7.2 and three times on PHP 7.3, and compared the numbers.
PHP 7.2 average: 192 requests per second
PHP 7.3 average: 224 requests per second
The results were consistent with very small variation. WordPress with WooCommerce running PHP 7.3 outperforms PHP 7.2 by 16.67%.
So what are you waiting for? It is time to get that extra performance boost. Upgrade your site to be PHP 7.3 compatible today, and get the 10-17% extra performance boost!”
From hackernoon.com we get the features listed below:
Not having an adequate way to handle errors when using JSON has been a problem for quite a long time, and web developer all over the worlds have seen this as a huge downside of the language,
The RFC of PHP 7.3 has accepted this update by a 23 vs 0 vote which says how much this feature has been requested.
Until PHP v7.2 we needed to use a workaround to get an error from JSON and it was not reliable nor proficient in its job;
The new flag I am about to show you is an excellent alternative because give to the programmer the opportunity to use the power of exceptions that can be managed within the “try-catch” block of code.
A countable element in your code can be a variable with an array format or an object whose class is implementing the Countable interface.
Last year PHP 7.2 added a warning that shows up whenever the web developer was counting or trying to loop an uncountable element.
It is possible to solve this problem and one of the best solutions currently used is to apply a check like a snippet below:
The code checks whether the variable is an array or is an instance of the Countable interface.
The is_countable function takes a variable as a parameter and then return a boolean depending if the function is countable or not.
There is no restriction about the format the parameter has to be, of course, if you put a non-countable variable the return will be false.
As per version 5.6 of PHP, there are over 75 built-in functions that belong to the arrays’ category.
Despite the vast numbers of tools available, at the moment, if we need to retrieve the first or the last key of an array we have to get all the keys using array_keys()and only then go for the first or last values of the array.
Another way is to opt for end()or reset().
As you may know, all the methods just described modifying the array pointer, which is something that (other than be resources consumer) you just may not want to do.
The RFC of the upcoming version proposed the introduction of 4 brand-new methods the were set to solve this issue.
The four methods were:
Among the four of them, only the one set that fetches the keys were accepted with 18 to 14 votes.
They work for both numeric and associative arrays.
The same would have worked for the other two functions illustrated in this chapter array_value_*
Just to be clear, let me repeat,
Those functions have been refused with 18 no and 15 yes.
In my opinion, these two functions would have been useful as well but according to several web developers, in certain cases, the value returned would have been ambiguous.
Here is why:
An additional option that I come across browsing on forums and talking to other web developers was to return a tuple like [$key => $value].
Even though this option will not be available on the new version, seeing the favourable responses, it might arrive with the following RFCs.
Since this is a function that did not exist before there are not going to be any backwards compatibility problems, the only issue could arrive if you have created and you are using your own version of array_key_first()and array_key_last().
Deploy secure application must always be the main focus of every programmer.
One task that each of us is facing of daily basis it to diminish the risk of CSRF and information leakage attacks.
Same-site cooking declares that cookies must be sent only with request initiated from the same domain.
This is not an official standard but Google Chrome and several of the best PHP frameworks already implement it whereas Firefox and new version of other frameworks confirmed that they are planning to do so.
Currently, cookies are issued by the set-cookie header, a web developer can set a key-value pair alongside flags for the browser in order to agree if a cookie should be available or not.
This way to do things allows a vulnerable access to CSRF attacks.
The new RFC adds is suppose to solve the problem is a non-breaking mode by adding a new parameter and also modify four main functions of the language.
Two ways were proposed.
Adding a new argument to the function or allowing an array of option for moving all the options of the cookies inside.
How it will work?
Two values can be added to the same site flag present in the above functions
They are Lax and Strict.
Cookies that are using Lax will be accessible in a GET request that comes from another domain, while on the contrary Strict will not be accessible in a Get request.
Include features that Increase security in the code seem always a no-brainer but as always before deciding to apply them in our scripts we need to properly evaluate the pro and the cons of our choices
The main risk implied for using the same site flag as a supplementary argument to those functions is that it might never become an official standard.
It means that eventually browser will downturn the flag.
If this happens and you have already implemented it, it will result in you applications stuffed with junk code that need to be removed.