I was buying a domain and I need to verify the history of the domain in-terms of 302 redirects on the domains. is there any way by which I can check a domains history
There are tools and sites available through which you can check their NS records which can be used before for redirection rules as per their name servers also some paid tools are available to get the entire domain history
Check whoisrequest.com and go to domain history.
Check archive.org if you would like to check what type of site it was
Check research.domaintools.com/research/hosting-history/ to get entire data
hope it helps!
Related
I am attempting to view subdomain data in GA4. My client has a main site, with several additional subdomains all using the same gtag.js tag (I confirmed that they are all using the same gtag). When I view data in Google Analytics, I'm not seeing the subdomain URLs.
I have attempted the following to access the data:
I set up the primary domain as an "Unwanted Referral", though I was not seeing the subdomains listed when viewing Reports > Acquisition > Traffic Acquisition > Type Referral in the local search > Switch Session Default Channel Group to Session source/medium).
I set up a segment: (Sessions > Hostname > subdomain url) but am not seeing the subdomains listed in the auto-populate dropdown. When I enter the subdomain manually, no data is shown.
The subdomains are showing as indexed in Google Search Console.
I confirmed that the site is using the correct configuration of Google's Global Site Tag (gtag.js). Specifically, the default setting of the cookie domain parameter is set to 'auto'.
I would expect to see subdomain data in Google Analytics, but am not getting anything. Would it be better to set unique accounts for each subdomain?
Cookie domain shouldn't matter here. GSC most definitely does not matter. Referral traffic shouldn't matter either. The start of your debugging should really be looking at all the distinct values of the hostname dimension.
If you don't see your hostname there, then the next step is verifying proper tracking on the missing hostname. Go there, pay attention to the tid value in the network request to google's collect endpoint. The tid should be exactly the same as the tid of the main site, unless you're using a different source for the subdomain, but it's unlikely.
Wrong tid is the most probable issue. If it's exactly the same, then check the dl field in the network request. Make sure it contains correct subdomain.
The next step I would take is checking the Filters of the property you're looking at. Make sure you're not filtering your traffic out.
If these don't help and you still have the issue, make the screenshot of your explorer where you pull out the hostname dimension by hit and show the screenshot of the ga4 event that you believe should be displayed there.
As part of the upcoming changes to Facebook Ads, you now must verify ownership of your domain name.
We operate a SaaS platform where user content is hosted on subdomains (myaccount.example.com etc). We need these users to be able to verify ownership of their domain so they can track their own events. We have enabled them to add the meta tag on their domain, and this verifies okay.
<meta name="facebook-domain-verification" content="codefromfbhere" />
However, the problem is, when you go into 'Events manager' -> 'Aggregated event measurement' -> 'Configure web events', it shows me the root domain instead of the subdomain I just verified (e.g. example.com instead of myaccount.example.com).
This is possible, as Leadpages has achieved the same goal. When you add in a Leadpages subdomain, you're able to verify it via meta tag, and it shows the subdomain in the 'Web event configurations' area.
I don't see any extra headers that they have provided or anything else that would enable this.
How do you mark subdomains as independent from the eTLD+1?
I wanted to chime in with the perspective of someone who works for Facebook. For most businesses, even ones that host pages for other businesses, Aggregated Event Measurement without anything extra is the correct solution.
Advertisers who do not own their own domains will not be able to verify the domain for the purpose of event configuration in Ads Manager. Advertisers may consider purchasing their own domain to continue running their campaigns uninterrupted, or moving toward link clicks/landing page views for campaign optimization and reporting. We are currently investigating other solutions for this use case but do not have any additional information to share at this time.
For a very small number of businesses already on the Public Suffix List (PSL) subdomains will be able to get data as if they were a root domain. This is because being on the PSL basically makes the root domain name act as if it was a TLD (such as “co.uk“ or ”gov.au“). In almost every case it does not make sense for sites to request to be added to the PSL as this dramatically changes how the Public Suffix listed domain name will function.
The PSL process is intended only for platform providers that provide subdomains for large numbers of small businesses which really ought to be treated as though they were in fact separate domains.
The Public Suffix List is not useful, nor intended to be used as a means to gain additional subdomain events reporting. Adding a domain name to the PSL means that there will be total cookie separation between subdomains and that cookies will become disabled on the root domain. If you a domain gets added to the PSL you'll not have much control for that site itself. For example, if you have a /login page on that domain. This may not work as it does today if you proceeded with a PSL addition, as cookies may get disabled on the root domain.
It’s also important to note that browsers will enforce the behavior described based on their own update cadence of the PSL. Some browsers don't update their lists more regularly than bi-annually. This means that if you're on the list and a browser updates their copy of the list, and you later decide to not be on the list, there may not be an easy way to back out the effects; it's not as simple as submitting another request to get taken off of the list.
More information can be found at Facebook’s help center article here.
[Update Mar 19 2021]
Facebook just announced they will be supporting the Public Suffix List for domain verification and event configuration. This means that merchants using a registered domain on the Public Suffix List will be able to use that domain for verifying and configuring their top 8 events on the domain. For example, if myplatform.com is a registered domain on the Public Suffix List, then Jasper, a merchant with the subdomain jasper.myplatform.com, would now qualify as an effective eTLD+1 and would be able to verify "jasper.myplatform.com" and use it to configure their top 8 events in the web events configuration tool.
Read more here:
https://developers.facebook.com/docs/sharing/domain-verification
[Original Answer]
For the upcoming changes for Apple iOS 14.5, you can only verify root domain, which is example.com in your example in order to setup the web event configurations.
The only way you can do this is provide your client's a way to buy/setup their own domain on your service.
You may watch the webinar recording here
https://www.facebook.com/business/m/sessionsforsuccess
My website is JerryDelRio.com – it's wordpress install looks clean, but it appears that malware exists on all sub-domains in their idxbroker.com search. For example:
http://www.jerrydelrio.idxco.com/idx/14511/mapSearch.php
How can we make google realize that these sub-domains are good to go? Idxbroker.com is a service we use to display property real estate search – I do NOT control that domain and I am sure it is very clean.
Here is a screenshot on how to submit review request to google:
But it ask to upload verification file to jerrydelrio.idxco.com. But i don't control the domain. It is just a service from Idxbroker.com
Please help me on how i can request google to review the Reported Attack page.
Thanks for your time.
You should move this account to a custom subdomain via a CNAME record. Then you can claim in google webmasters tools.
Two sites, with very similar content. Both existing and well established. I've set up 301 redirects to site A from site B.
Should I use the Webmaster 'change of address' feature to support the merge?
From what I've read, it seems more suited to an old domain transferring to a new domain. Thoughts?
The use the change of address tool in Google Webmaster will help you to manage the transition needed by Google to index your new URLs at the new address, while minimizing impact to your current ranking in the SERP.
You can use it together with a "Standard" 301 Moved Permanently redirect, which will pass Page Rank from site A to site B.
I'm running a print campaign and have bought a specific URL to try and measure the efficacy of that advert.
I'm using cPanel and Google Analytics.
I want people to type in the new, advert specific URL and be redirected to my actual, live domain name and I would like it to show up in Google analytics as a referrer so I can track how many people visit that website address.
I haven't a single idea how to do this properly. i've set it up as an addon domain in cPanel, and have also set it to redirect to my main URL from within cPanel, but at first glance in "real time" and "traffic sources" it just says "direct", but I want it to show this URL.
So to sum up, I want people to type in a URL, it then redirect and for it to show up in analytics as a referrer, by name. Thanks in advance!
I've done it, and here's how I did it:
I set the domain name up as an addon domain on my cpanel account.
Then I created a .htaccess in the root of that subdomain, with the following content:
# Permanent URL redirect
Redirect 301 / http://www.DomainName.co/?utm_source=Domain-Name.co.uk&utm_medium=mediumName&utm_content