finchgreenber.livejournal.com
Open in
urlscan Pro
81.19.74.4
Public Scan
URL:
https://finchgreenber.livejournal.com/profile
Submission: On February 02 via manual from US — Scanned from IT
Submission: On February 02 via manual from US — Scanned from IT
Form analysis
4 forms found in the DOMGET //www.livejournal.com/rsearch/
<form class="s-header-search__form ng-pristine ng-valid" action="//www.livejournal.com/rsearch/" method="get" role="search" target="_blank">
<input type="hidden" name="journal" value="finchgreenber" autocomplete="off">
<input type="hidden" name="journalId" value="90307666" autocomplete="off">
<button class="
s-header-search__btn
s-header-search-btn" type="submit"><span class="
i-iconus
s-header-search__icon
">
<svg xmlns="http://www.w3.org/2000/svg" class="svgicon flaticon flaticon--search" width="16" height="16">
<use xlink:href="#flaticon--search"></use>
</svg>
</span>
</button>
<input class="s-header-search__input" type="text" placeholder="Search" results="5" autosave="some_unique_value" size="12" name="q" id="SearchText">
</form>
GET //www.livejournal.com/rsearch/
<form class="s-header-search__form ng-pristine ng-valid" action="//www.livejournal.com/rsearch/" method="get" role="search" target="_blank">
<div class="s-header-search__form-content">
<input type="hidden" name="journal" value="finchgreenber" autocomplete="off">
<input type="hidden" name="journalId" value="90307666" autocomplete="off">
<div class="s-header-search__input-wrapper">
<input class="
s-header-search__input
s-inline-search-input" type="text" placeholder="Search" results="5" autosave="some_unique_value" size="12" name="q" id="SearchText" required="">
</div>
</div>
<button class="
s-header-search__btn
s-do-item-search-btn" type="button" data-tour="friendsfeed" data-tour-start-page="^/feed" data-tour-step="2" data-tour-bubble="{
"aside": true,
"alwaysBottom": true,
"alwaysLeft": true,
"forceY": 10
}" data-tour-title="tour.friendsfeed.title" data-tour-text="tour.friendsfeed.step2.search.tip"><span class="
i-iconus
s-header-search__icon
">
<svg xmlns="http://www.w3.org/2000/svg" class="svgicon flaticon flaticon--search" width="16" height="16">
<use xlink:href="#flaticon--search"></use>
</svg>
</span>
</button>
</form>
POST https://www.livejournal.com/login.bml?ret=1
<form action="https://www.livejournal.com/login.bml?ret=1" method="post" class="b-loginform__form pkg lj_login_form ng-pristine ng-valid ng-valid-maxlength">
<input type="hidden" name="ref" value="" autocomplete="off">
<input type="hidden" name="ret" value="1" autocomplete="off">
<div class="b-loginform__form-wrap">
<div class="b-loginform-field" ng-class="{'b-loginform-field--error' : loginForm.errorUsername}">
<div class="b-loginform-field__wrap">
<div class="b-loginform-field__icon-wrap b-loginform-field__icon-wrap--user">
<svg xmlns="http://www.w3.org/2000/svg" class="svgicon flaticon flaticon--userhead" width="16" height="16">
<use xlink:href="#flaticon--userhead"></use>
</svg>
</div>
<input id="user" class="b-loginform-field__input b-loginform-field__input--user ng-pristine ng-untouched ng-valid ng-empty ng-valid-maxlength" type="text" tabindex="10" placeholder="Username" value="" name="user" size="18" maxlength="17"
autocorrect="off" ng-model="loginForm.model.username" ng-init="loginForm.model.username=null">
</div>
<span ng-bind-html="loginForm.errorMessage" class="b-loginform-field__errorMsg ng-binding ng-hide" ng-show="loginForm.errorUsername"></span>
</div>
<div class="b-loginform-field" ng-class="{'b-loginform-field--error' : loginForm.errorPassword}">
<div class="b-loginform-field__wrap">
<div class="b-loginform-field__icon-wrap b-loginform-field__icon-wrap--pass">
<svg xmlns="http://www.w3.org/2000/svg" class="svgicon flaticon flaticon--lock" width="16" height="16">
<use xlink:href="#flaticon--lock"></use>
</svg>
</div>
<input id="lj_loginwidget_password" class="b-loginform-field__input b-loginform-field__input--pass ng-pristine ng-untouched ng-valid ng-empty ng-valid-maxlength" type="password" tabindex="11" name="password" size="20" maxlength="30"
placeholder="Password" ng-model="loginForm.model.password" ng-init="loginForm.model.password=null">
</div>
<span ng-bind-html="loginForm.errorMessage" class="b-loginform-field__errorMsg ng-binding ng-hide" ng-show="loginForm.errorPassword"></span>
</div>
<div class="b-loginform-other-field" ng-init="loginForm.forceRemember = 0">
<!-- ngIf: !loginForm.forceRemember -->
<div class="b-loginform-checkbox ng-scope" ng-if="!loginForm.forceRemember">
<input id="remember_me" class="b-loginform-checkbox__input b-ljform-checkbox ng-pristine ng-untouched ng-valid ng-not-empty" type="checkbox" tabindex="12" name="remember_me" ng-model="loginForm.expire">
<label class="b-loginform-checkbox__label" for="remember_me">Remember me</label>
<label class="b-loginform-checkbox__control" for="remember_me"></label>
</div><!-- end ngIf: !loginForm.forceRemember -->
<a class="b-loginform__link" href="https://www.livejournal.com/lostinfo.bml" title="Forgot password" tabindex="13" target="_self">
Forgot password
</a>
</div>
</div>
<!-- ngIf: loginForm.presubmitWarning -->
<button type="submit" name="action:login" class="b-loginform-btn b-loginform-btn--login b-loginform-btn--auth b-loginform-btn--center b-loginform-btn--disabled" tabindex="14" ng-click="loginForm.loginUser($event)"
ng-class="{'b-loginform-btn--disabled' : !(loginForm.model.username && loginForm.model.password) }"> Log in </button>
</form>
POST https://www.livejournal.com/identity/login.bml?type=openid&auto_forwhat=user%24finchgreenber%24%2Fprofile
<form action="https://www.livejournal.com/identity/login.bml?type=openid&auto_forwhat=user%24finchgreenber%24%2Fprofile" method="post" class="lj-openid-auth b-loginform__form ng-pristine ng-valid">
<div class="b-loginform-field" ng-class="{'b-loginform-field--error' : loginForm.errorId}">
<div class="b-loginform-field__wrap">
<div class="b-loginform-field__icon-wrap b-loginform-field__icon-wrap--openid">
<svg xmlns="http://www.w3.org/2000/svg" class="svgicon flaticon flaticon--openid" width="16" height="16">
<use xlink:href="#flaticon--openid"></use>
</svg>
</div>
<input type="text" size="18" id="openid" name="openid:url" class="b-loginform-field__input ng-pristine ng-untouched ng-valid ng-empty" placeholder="Your openid url" tabindex="10" ng-model="loginForm.model.openid"
ng-init="loginForm.model.openid=null">
</div>
<span ng-bind-html="loginForm.errorMessage" class="b-loginform-field__errorMsg ng-binding ng-hide" ng-show="loginForm.errorId"></span>
</div>
<button type="submit" name="action:login" class="b-loginform-btn b-loginform-btn--login b-loginform-btn--center lj-openid-auth-submit b-loginform-btn--disabled" tabindex="11" ng-class="{'b-loginform-btn--disabled' : !loginForm.model.openid}"
ng-click="loginForm.loginOpenID($event)">Log in</button>
</form>
Text Content
? LiveJournal * Find more * Your 2021 in LJ * Comunità * RSS Reader * Shop * Aiuto * Accedi * * Accedi * Join free Join * * Italiano (it) * English (en) * Русский (ru) * Українська (uk) * Français (fr) * Português (pt) * español (es) * Deutsch (de) * Italiano (it) * Беларуская (be) LOG IN No account? Create an account Remember me Forgot password Log in Log in Facebook Twitter Google RAMBLER&Co ID By logging in to LiveJournal using a third-party service you accept LiveJournal's User agreement No account? Create an account * Aggiungi agli Amici * Add Note Add note * View friends feed * Track User * Invia messaggio * Invia regalo finchgreenber FINCHGREENBER'S JOURNAL Account Creato il 2 Febbraio 2022 (#90307666) mai aggiornato Gift Nome: finchgreenber Località: Louisiana, United States Sito: https://oxfarm45.bloggersdelight.dk/2022/02/02/zoekmachine-optimalisatie-seo-4-stappen-naar-snelle-seo/ External Services: * finchgreenber@livejournal.com * Bio A BIASED VIEW OF ZOEKMACHINE OPTIMALISATIE - BETER VINDBAAR IN GOOGLE MET SEO Google Zoekexperimenten: van ideen tot lancering, Google, geraadpleegd op 19 januari 2020 (en) Utilizing website speed in web search ranking. Google. Geraadpleegd op 3 februari 2021. Google Page, Speed Insights (16 april 2014). Toelichting Google op gebruik abundant bits (16 april 2014). Google gaat mobile friendly websites bevoordelen in Zoekresultaten (12 maart 2015). Zoekmachine optimalisatie: hoger in Google - YURIBITE: Online Scoren Gearchiveerd op 2 februari 2017. Geraadpleegd op 27 januari 2017. (en) Irrelevante meta tags onwettig verklaard in Duitsland (9 augustus 2004). Gearchiveerd op 12 januari 2012. Geraadpleegd op 18 april 2011. David Kesmodel, Sites Get Dropped by Online Search Engine After Trying to 'Optimize' Rankings. (22 september 2005). Geraadpleegd op 18 april 2011. Penenberg, Legal Showdown in Search Fracas. Wired Publication (8 september 2005). Gearchiveerd op 6 september 2008. Geraadpleegd op 18 april 2011. Matt Cutts, Confirming a charge. mattcutts. com/blog (2 februari 2006). Gearchiveerd op 26 juni 2012. Geraadpleegd op 18 april 2011. Interaction in other languages, Matt Cutts, 9 december 2006 Ban voor Blackhat SEO Parocom, Marketsharer, 29 maart 2009 Google web designer tools. Yahoo! Website Explorer. Gearchiveerd op 17 april 2011. Geraadpleegd op 18 april 2011. Bing Tool kit. Geraadpleegd op 18 april 2011. MORE ABOUT ZOEKMACHINE OPTIMALISATIE (SEO) - HOGERE POSITIES - JEROME We hebben toddler hier gesproken over 'zoekmachines' en 'zoekmachine optimalisatie'. Maar zoals je wellicht weet is er maar n zoekmachine pass away wereldwijd de toon voert: Google. In Nederland gebruikt ongeveer 95% van de internetgebruikers Google als zoekmachine en slechts 5% gebruikt Bing. Zoekmachine optimalisatie zet je dus voornamelijk in om beter gevonden te worden in Google. Zoekmachine Optimalisatie (SEO) - Admeisters Waarom niet optimaliseren voor andere zoekmachines? Algoritmes van andere zoekmachines werken in de kern hetzelfde, maar hun algoritme simpelweg minder ver ontwikkeld is dan die van Google. Dus waar Google nu is, zijn andere zoekmachines misschien volgend jaar, of nog later. Referentie , met het optimaliseren van je site voor het algoritme Google zit je altijd goed. Dus optimaliseren voor het Google van nu, betekend optimaliseren voor andere zoekmachines in de toekomst. Het algoritme van Google is een complexe reeks aan berekeningen pass away gezamenlijk zorgen voor rangorde in de zoekresultaten. Hoe het algoritme er precies uitziet is niet bekend en houdt Google geheim. Toch is er veel wl bekend. FRIENDS: * Friends 1 finchgreenber COMMUNITIES: * Watching 2 lj_releases, news STATISTICS APPLICATIONS * iOS * Android * Huawei SEGUICI: * Seguici su Facebook * Seguici su Twitter LiveJournal COMPANY * Chi Siamo * News * Aiuto PRODUCTS * Button "Share" COMMUNITY * Frank CHOOSE LANGUAGE English Deutsch Dansk español Français Italiano Русский Українська Беларуская 日本語 Português Esperanto עברית Nederlands Magyar Gaeilge íslenska suomi Ελληνικά Norsk bokmål Svenska polski 简体中文 Latviešu Türkçe Bahasa Melayu हिन्दी Brazilian Portuguese Chinese Traditional Lietuvių Norsk nynorsk Italiano ▾ * English * Deutsch * Dansk * español * Français * Italiano * Русский * Українська * Беларуская * 日本語 * Português * Esperanto * עברית * Nederlands * Magyar * Gaeilge * íslenska * suomi * Ελληνικά * Norsk bokmål * Svenska * polski * 简体中文 * Latviešu * Türkçe * Bahasa Melayu * हिन्दी * Brazilian Portuguese * Chinese Traditional * Lietuvių * Norsk nynorsk v.545 Privacy Policy Termini e condizioni Aiuto