Blog

What is off page SEO – Search Engine Optimization
There are multiple type of SEO. Here we will about the Off page SEO.

Off page SEO is not done on website directly. Its done in multiple ways. Some of list is as follow
- Off page SEO is done by doing link building
- By sharing web link with public by using multiple portals
- Submitting link on multiple web directories
- Submitting link on search engine
- Search of local area website and post our web link for local areas
February 27, 2017
What is on page seo – Search engine optimization
On page SEO is defined on website itself. There can be multiple factor that where content needs to be put on web page.

In on page seo , all SEO related activies are done on web page source code. Below are the few things which we must take care for on page SEO
- Title of page
- Description of page
- Tags Description
- Keywords Description
- Meta keywords and description
- Internal Linking of web pages
- Images tags
February 27, 2017
What is the backend process of SE – Search Engine
Search Engine is working for all web pages in below ways
- Search Engine crawls the complete website and fetches all urls from the web pages. If we talk about google then google performed this crawl by GOOGLEBOT.
- Search Engine create index for all the web pages and enter this information into own database. Whenever any user search any information then Search Engine sends the request to database indexing and fetch the result and displayed it to end user.
- There can be multiple result based on required search string. So Search Engine shows all result to end user based on rank of pages. This process is called calculation of relevant pages. Rank of pages means position of the page on search engine
Major Search Engines change their searching algorithm continuously sometimes multiple time in a day. and its done just because user should update their websites time by time.
February 27, 2017
What is the need of SEO – Search Engine Optimization
SEO stands for Search Engine Optimization. We do SEO for multiple reasons. Below are the few one
- To give good rank to our website
- To provide high and good quality traffic to our website
- To get listed website on the top of search engines.
- To reach the target public for which website is prepared
February 27, 2017
What is Cross-Browser testing
What should we validate in Cross-Browser testing? As far as, I have found a way on this, my understanding is as below with each category explained on its approach:

Validating CSS

Page Element Operations (E.g. Click, LoseFocus, Submit etc) on plain browser or without JS

Images and their URLs

Font sizes (from browser)

Zoom behaviours by browser

All Links Validation (Recursively)

Text/Images and their alignment

Shift text positions

DATEs format validation

Page design in Mobile/Portrait/Landscape View

Multi-byte/Special Characters
February 27, 2017
How to Log in GIT

LOG
View whole commits history
git log
View last n commits with its message only
git log –oneline -n
E.g.
git log –oneline -n 2
View commits history with differences (-p) only upto two last commits (-2)
git log -p -2
View commits history with statistics
git log –stat
View commits history beautifully in one-line, short status, full status, or max status
git log –pretty=[oneline/full/fuller/short]
View commits history in pretty format having (short-hash, author-name, author-date, subject)
git log –pretty=format:”%h – %an, %ar : %s”

— with date-range
git log –pretty=format:”%h – %an, %ar : %s” –author=pgupta –since=”2017-01-01″ –before=”2017-01-31″ –no-merges
Graphical (ASCII) presentation commands
git log –graph –topo-order –decorate –oneline –all
git log –graph –topo-order –decorate –oneline –boundary master..dev
git log –graph –all –topo-order –decorate –oneline –boundary –force-branch-columns=master,develop
List local branches with corresponding HEAD hash, sorted by last commit date
git for-each-ref –sort=-committerdate refs/heads/

February 27, 2017
How to Tag in GIT
TAGGING A GIT BRANCH

Show all tags
```
git tag
```
Search tag
```
git tag -l "tag-search-pattern"
```
```
E.g.
```
```
git tag -l "v2.0.2*"
```
Create annotated tag
```
git tag -a <tagname> -m "<message>"
```
```
E.g.
```
```
git tag -a v2.0 -m "This version 2.0 contains web-ui changes"
```
Show tag details
```
git show <tagname>
```
```
E.g.
```
```
git show v2.0
```
Checkout tags
```
git checkout -b <branchname> <tagname>
```
```
E.g.
```
```
git checkout -b version2.0 v2.0
```
Pushing tags to remote
```
git push origin <tagname>
```
```
E.g.
```
```
git push origin v2.0
```
Pushing all (un-pushed) tags to remote
```
git push origin --tags
```
Rename an annotated git tag
- rename tag
```
git tag <new-tag> <old-tag>
```
```
E.g.
```
```
git tag v1.1 1.1
```
- delete tag locally
```
git tag -d <old-tag>
```
- push deleted tag-change to remote
```
git push origin :<old-tag>
```
```
E.g.
```
```
git push origin :refs/tags/1.1
```
```
OR
```
```
git push origin :1.1
```
- push renamed tag to remote
```
git push origin <new-tag> (E.g. git push origin v1.1)
```
```
OR
```
```
git push --tags
```
- Finally, make sure that the other users remove the deleted tag. Please tell them(co-workers) to run the following command:
```
git pull --prune --tags
```
List local branches with corresponding HEAD hash, sorted by last commit date
```
git for-each-ref --sort=-committerdate refs/heads/
```
February 27, 2017
How to Compare Branch in GIT
COMPARE BRANCH
- Compare two branches (local) and show how much commits each branch is ahead of the other
```
git rev-list --left-right --count <branch1>...<branch2>
```
DIFF STATUS
- Get differences status between local (checked-out) branch and its respective remote (tracked) branch
```
git checkout <local-branch>
```
```
git status -sb
```
```
Example Output: ## <local-branch>...<remote-branch> [ahead 2, behind 1] 
```
DIFF AHEAD revisions of local branch
- To see differences of ahead-revisions (in local-branch)
```
git diff <local-branch>...<remote-branch>^
```
```
E.g.
```
```
git diff master...origin/master^ 
```
DIFF BEHIND revisions of REMOTE branch
- To see differences of ahead-revisions (in local-branch)
```
git diff <remote-branch>...<local-branch>^^
```
```
E.g.
```
```
git diff origin/master...master^^
```
February 27, 2017
How to List all Remote Branches in GIT
- List all remote branches
```
# Show only remote branches names
```
```
git remote
```
```
# Show remote branches names with links
```
```
git remote -v
```
- Update everything on local from remote
```
git remote update
```
```
* This command will update the local repository with ALL the content at ALL those remotes at git server. It would not show any changes to your local repository but in fact, it would update and create new remote branches in local .git folder. Now whenever we would create a local branch which is already existing at remote, it would fetch from .git folder straightaway to fetch all the contents.
```
- Rename remote branch name
```
git push origin :<old_name> <new_name>
```
- Delete remote branch
```
git push origin --delete <remote-branch-name>
```
- Pull remote branch to create local
```
git pull <repo-name> <remote-branch-name>:<local-branch-name>
```
```
E.g.
```
```
git pull origin develop:develop
```
```
git pull origin features/test/tasks:features/test/mylocaltasks
```
- Clean up stale references i.e. Remove all outdated-references from local machine’s cache (i.e. remote/* kind of heads)
```
git remote prune origin
```
```
OR
```
```
git fetch -p
```
February 27, 2017
How to Rename Branch in GIT
- Rename currently checked-out local branch
```
git branch -m <new-branch-name>
```
- Rename local branch
```
git branch -m <branch_name_to_rename> <new-branch-name>
```
- push new branch name to remote
```
git push origin :<old_name> <new_name>
```
- Rename branch locally and remotely in 3 steps
```
# Rename branch locally
```
```
git branch -m <old-branch-name> <new-branch-name>
```
```
# Delete the old branch
```
```
git push origin :<old-branch-name>
```
```
# Push the new branch, set local branch to track the new remote
```
```
git push --set-upstream origin <new-branch-name>
```
```
OR
```
```
git push -u origin <new-branch-name>
```
- Reset the upstream branch for the new-name local branch.
  - Switch to the branch
    
    git checkout <new_name>
  - Push new branch-name now
    
    git push origin -u new-name
February 27, 2017