Suggestion for custom URL import

seoaddict

Hi again @sven,

I have another suggestion, not sure if it would be viable, but could potentially help many users. There are some links I use for Tier 1 in SER. Also, I use SER for distributing posts to my network.

The anchors for these links are often specific per domain, as different domains have different metrics and warrant different types of specific anchor texts.

As it stands now, I have to put 1 anchor in, then import 1 URL to post, then switch anchor, and so on. Note, I use the project URL section for both URL and anchor, not the anchor section itself. (as in url#anchor at the top)

I'm wondering if you've considered a footprint like this (using a Wordpress post as an example):

https://project-url.com/#anchor#https://imported-target-url.com/wp-admin/

The second "#" could be changed to any viable footprint that would work. I only used "#" as an example.

What this would allow is for us to "pair" anchors and target URLs together, to avoid having to re-open projects and manually switch URLs.

You could insert many URLs like:

wp-admin/https://project-url.com/#anchor1#https://imported-target-url.com/wp-admin/<br>https://project-url2.com/#anchor2#https://imported-target-url2.com/

Or using spintax:

wp-admin/https://project-url.com/#{brand|brand2}#https://imported-target-url.com/wp-admin/<br>https://project-url2.com/#{keywrd|keyword2}#https://imported-target-url2.com/

And so on. Unchecking the "random URL" box accomplishes this to some extent, but, if a target URL fails, for example, I'm pretty sure it uses the anchor/URL that should've been on that target on the next target.

The method I've described above would be "locked" to specific domains, meaning that if the URL fails to post, that anchor simply does not get posted at all, and SER moves on to the next URL/target combination.

SER would have to "understand" that using the "second footprint" indicates that a target has been specified... so not sure if that would even be possible.

Thanks for reading, let me know what you think!

Sven

wouldn't it be more logical to bing anchors with imported target urls instead?

like import target urls as this:

<span class="com">https://imported-target-url.com/wp-admin/[<b>anchor.that.overwrites.the.one.in.project</b>]</span>

seoaddict

Sven said:

wouldn't it be more logical to bing anchors with imported target urls instead?

like import target urls as this:

<span>https://imported-target-url.com/wp-admin/[<b>anchor.that.overwrites.the.one.in.project</b>]</span>

This would definitely work as well. But it would be better if there was a way to override the URL in the project as well. I.e., subpages could be imported along with homepages or various other URLs.

https://imported-target-url.com/wp-admin/[https://www.google.com/#Google]
https://imported-target-url.com/wp-admin/[https://www.google.com/#{Google|Google.com}]

https://imported-target-url.com/wp-admin/[https://www.facebook.com/profile23#Profile23]
https://imported-target-url.com/wp-admin/[https://www.facebook.com/profile23#{Profile23|Facebook}]

That's a pretty damn smart footprint if I'm honest, could just have any imported URLs with the structure of the project URL/anchor text (surrounded by []) override the project settings.

seoaddict

If the URL override makes it a lot more difficult to implement, just the anchors would be fine. Would still save an unbelievable amount of time.

seoaddict

Hey @sven, since this feature seems sort of difficult to implement, I'm curious if I can get an answer on this:

It seems that SER processes imported URLs backwards, i.e., the last URL first and the first URL last. I don't really understand why as this seems counter-intuitive. Is there any way to make it so that SER processes URLs in the order they are imported?

Note: Randomize imported URLs is set to "NO". URL randomization is unchecked. I can confirm the URLs are imported in the proper order, but they are processed backwards no matter what I do.

This would help, at least with sites that I know are 100% online I can use the non-shuffle URLs feature and non-shuffle imported URLs to achieve what I need to do... at least until such a time as the mentioned feature above is implemented.

Example: Let's say I have a project with these URLs/anchors

http://www.domain.com/#Anchor1
http://www.domain.com/#Anchor2
http://www.domain.com/#Anchor3

And I import these target URLs:

http://www.target1.com/wp-admin/
http://www.target2.com/wp-admin/
http://www.target3.com/wp-admin/

SER will process them like this:

http://www.domain.com/#Anchor1 -> http://www.target3.com/wp-admin/
http://www.domain.com/#Anchor2 -> http://www.target2.com/wp-admin/
http://www.domain.com/#Anchor3 -> http://www.target1.com/wp-admin/

Expected processing (how it should be - unless I'm missing something) would be like this:

http://www.domain.com/#Anchor1 -> http://www.target1.com/wp-admin/
http://www.domain.com/#Anchor2 -> http://www.target2.com/wp-admin/
http://www.domain.com/#Anchor3 -> http://www.target3.com/wp-admin/

They are processed in the opposite order of what is expected.

Sven

The reason is simple, SER opens the file, jumps to the <end - 1MB> of the file and reads 1MB from it. Then it truncates the file on <size - 1MB>. This way it is never wasting resources or memory.

If it would read from the beginning, it would need to rewrite the complete file and read onwards to the end and that would waste a lot resources and memory.

seoaddict

Sven said:

The reason is simple, SER opens the file, jumps to the <end - 1MB> of the file and reads 1MB from it. Then it truncates the file on <size - 1MB>. This way it is never wasting resources or memory.

If it would read from the beginning, it would need to rewrite the complete file and read onwards to the end and that would waste a lot resources and memory.

Actually it seems that there is no set order when processing URLs. I tried to import the URLs in reverse order, but it still processes them in a random order. Why would this happen if the imported URLs are not randomized?

If there is no way to match URLs and anchor text on submission, could I donate some money for you to add the footprint? Just PM me and let me know how much money you'd need to add this sort of thing (if you're interested).

Preferable footprint:

https://imported-target-url.com/wp-admin/[https://www.google.com/#Google]
https://imported-target-url.com/wp-admin/[https://www.google.com/#{Google|Google.com}]

https://imported-target-url.com/wp-admin/[https://www.facebook.com/profile23#Profile23]
https://imported-target-url.com/wp-admin/[https://www.facebook.com/profile23#{Profile23|Facebook}]

Sven

well the loaded urls from file are sorted as well internally...that sorting is based on a random hash algorithm to not have the same order.

that special import format might get added...you can donate if its added

seoaddict

What’s the point of having “Randomize imported URLs” as a window/option if they’re already randomized via hash even if you press no? Seems like sorta just another button that has to be clicked before you can start a project... but from what I can tell it doesn’t do anything as the URLs are forcibly randomized (during processing, which is the only thing that matters). 

Sven

SER needs to sort the targets in some way to keep track of new and historic URLs. So it does this everytime a bit different whenever you start the project. It will then take the first URL, submit and then the next and so on.

Please simply take my words, it's not possible to change this behavior and not lose important resources.

Anyway, I promise to think about a solution to overwrite anchor/url on import of target urls with your format.

seoaddict

Alright, I will wait on the new format then and once it's implemented will send you a good sized donation for your time invested. Thanks!

Sven

I have added this format for next update, however it's not very much tested so I would really appreciate if you do this on your end.

seoaddict

@sven, just getting around to testing this now, sadly it does not work.

Input test:

</code>https://imported-target-url.com/wp-admin/[https://www.overwrite-project-url.com/#Overwrite-Project-Anchor]</pre>Output:<br><pre class="CodeBlock"><code><a href="https://www.overwrite-project-url.com/#Overwrite-Project-Anchor">overwrite-project-url.com</a>

Expected output:

<a href="https://www.overwrite-project-url.com/">Overwrite-Project-Anchor</a>

In the project settings, there is a URL/anchor combination of (this is there by default as I need something just to save the project).

overwrite-project-url.comhttps://www.overwrite-project-url.com/#

The override doesn't work at all, and SER thinks the URL is:

https://www.overwrite-project-url.com/#Overwrite-Project-Anchor

Instead of understanding that the "#" signifies that the end should be the anchor text. Essentially what it's doing is using the entire "override" URL footprint (including the anchor after #) as the URL, and the anchor included inside the project as the anchor instead of the override anchor.

Sven

ok so it's partly working with just the "overwrite-anchor" added to URL and not overwriting the original anchor? I will debug that and hopefully find the issue.

I swear it was working on my tests

Update: I found the issue and it should be fixed in next update.

seoaddict

Sven said:

ok so it's partly working with just the "overwrite-anchor" added to URL and not overwriting the original anchor? I will debug that and hopefully find the issue.

I swear it was working on my tests

Update: I found the issue and it should be fixed in next update.

Excellent, can’t wait to test. Thanks!

seoaddict

@sven Just got a chance to test this and it does seem that you've fixed it! Also tested using spun anchor texts and that works as well. Will send a donation in a bit once I get a chance to more thoroughly test it.