.png)
A young man identified as Tope
Adegbehingbe, has explained
why he killed his 86-year-old
neighbour, Mrs Janet Oyeniyi,
at Ajebambo village near
Oniparaga in Odigbo Local
Government Area of Ondo
State.
Adegbehingbe, who was
arraigned before an Akure Chief
Magistrates’ Court yesterday,
said he murdered the
octogenarian because he saw
her in his dream trying to kill
him.
Although Adegbehingbe’s plea
was not taken as the court has
no jurisdiction to entertain
murder trial, the accused,
however, said he took the
measure because the woman
was a witch. The accused said
he attacked the woman with
machete in early hours of that
fateful day.
In his confessional statement
made available to reporters at
Oke-Eda Magistrates’ Court in
Akure, yesterday,
Adegbehingbe confessed that
he was guilty of the murder
charge brought against him.
According to the prosecution
counsel, the accused was
alleged to have on 23rd of
October, 2015 at Ajebambo
camp via Oniparaga, Araromi
Obu in Odigbo Local
Government Area of the state,
killed one Mrs Janet Oyeniyi
with machete. The police also
told the court that
Adegbehingbe murdered the
86-year-old woman with
machete until she gave up the
ghost.
The offence, the prosecution
counsel said, was contrary to
and punishable under Section
319 of the Criminal Code Cap
37 Vol. 1, Laws of Ondo State of
Nigeria. Adegbehingbe said he
personally killed the woman
because he saw the deceased
in his dream trying to kill him.
He said:
“The woman happened to be
my neighbour. I killed her
because I saw her in my dream
trying to kill me. So
immediately I woke up the
following morning, I went
straight to her house to kill her
because I thought that was the
best thing to do before she
would kill me.” [NAN]
Naija wonder…. this is not
funny.
These are not the best of times
for popular Nollywood actress
Toyin Aimakhu who recently
packed out of her matrimonial
home over allegation of
infidelity on the part of her
husband, Adeniyi Johnson.
Few weeks after she left her
husband’s house, the actress
was said to have moved on with
Ebony Film Boss and ex-lover
Seun Egbegbe but the actress
denied the romance.
In a recent interview, Toyin
Aimakhu said she’s not dating
Mr Egbegbe while the Ebony
Film CEO confirmed their
romance to another media
outlet.
In the wake of the conflicting
interviews, Seun Egbegbe who
is reportedly funding Toyin
Aimakhu’s lavish lifestyle and
her movies was said to have
challenged her on why she’s
denying their romance openly,
this soon generated a hot
argument.
At a point, Toyin raised her
voice on him, telling him that
she couldn’t grant his request
because she just quit her
marriage and that people might
not see their romance in a good
light if they sensed she has
quickly rushed into another
relationship.
This was said to have infuriated
Seun who allegedly hit her and
beat her to a pulp.
Few hours after they both left
the ‘boxing ring’, Toyin packed
a few of her belongings and hit
Ibadan where her family resides
to console herself of the attack
and of course from those prying
her.
As it stands, her Instagram
followers are clueless on her
condition. She didn’t come to
her IG page for 3 days until few
hours ago when she shared a
old photo of herself to put to
rest the attack story.
Meanwhile, close friends who
broke this news to us swore
that the actress is not in
her right frame of mind
now. She has suddenly stopped
picking her calls.
One of our sources who is close
to Seun Egbegbe’s house in
Ikeja Lagos confirmed the
report from neighbours who
reportedly intervened at the
height of the attack.
No’ lele’ if she denies it, this is
the truth of the story sha
Website
URL
structure
is an
important part of SEO that is
underestimated by many.
Beyond putting keywords into
the URL, many don't give it
second thought. And yet, it is
one of the simplest and most
important things to optimize,
and plays an important part
in search results. Today, we
will discuss some URL
optimization techniques to
improve your websites'
rankings.
When talking about URL
structures, a few things come
to mind, namely the URL
length, keywords, sub-
directories, special
characters, and the effect of
each of them on direct traffic
as well as search visibility.
Let's start with the simplest
of them all.
URL Length
The URL length isn't a game
changer in search rankings,
but it still is an important
factor. Not to say that long
URLs don't rank well - they
can because it ultimately
boils down to the content. But
on average, the dominating
search results mostly
average between 35-40
characters.
Not only that, the URL length
is a major contributor when it
comes to direct traffic - i.e.
people who come over by
typing the URL into their
browsers. The shorter the
URL, the easier it is to
remember.
Sub-directories
URLs often contain many sub-
directories/sub-folders. This
very page you are on
contains two. 2015/ and 05/.
As far as hierarchies go, it is
OK to have as few as you
want, or as many as you can
manage. There is no co-
relation between the number
of sub-directories and search
rankings. However, there are
a few things to keep in mind.
Generally, from the user-
friendliness aspect, it is
considered as a good
practice to keep it simple. It
accounts for more direct
traffic. Also, it is advisable to
keep numbers out of URLs,
and generally go with easy to
read words. For blog posts,
you can either use a dated
structure such as
site.com/2015/05/article.html,
or category structure such as
site.com/how-to/article.html.
Personally, I prefer the latter,
but you can go either way.
Also, make sure that the
images you upload are
named properly, so that when
opened, their URL is readable
and looks decent.
Keywords
Having a keyword within your
domain name and URL is a
declining factor in rankings. It
is becoming less important
over time since Google is
placing more emphasis on
other search factors. When
you create URLs within your
site, don’t worry about
making them keyword rich. It
doesn’t hurt to add keywords
if it makes sense, but you
shouldn't stuff your URLs with
keywords, or they will seem
unnatural.
Special Characters
Sometimes you see strange
characters in URLs such as
&, %, $, and @. It is more
difficult for search engines to
crawl websites if their URLs
contain a lot of these special
characters. Consider the fact
that Google has gone on
record to state that you
should be using dashes over
underscores because it
affects how their search
engine reads the keywords in
your URL. This is how
seriously you should take
these special characters.
According to an estimate by
Neil Patel, only about 0.2% of
high ranking URLs have
special characters in them.
If you are using images, don't
let spaces come in when you
name them. "autumn-sunset"
is better than "autumn
sunset" because the space
gets replaced by special
characters.
Long story short, optimizing
your URLs can't hurt your
rankings. However, don't
focus too much of your
marketing efforts on your
URL structure because it
doesn’t impact rankings as
much as backlinks or content
quality. It is just there to give
you a small edge, so might as
well avail it when you can.
Most often when you insert a
Facebook JavaScript or
AdSense JavaScript in your
blogger template editor, you
often come across XML
Parsing errors that prompts
and says "The reference to
entity "version" must end
with the ';' delimiter." Blogger
blogs are coded in XHTML
and XML is quite strict in
following correct syntax
formatting than HTML. XML is
surely unforgiving in this
case. Blogger interprets all
your document as XML rather
than as HTML. XML is
PCDATA (Parsed Character
Data) by default which means
that XML parsers will
normally parse all the text in
a document. As a result when
we insert JavaScript inside
blogspot templates, all script
inside the JavaScript tags is
treated as a text and due to
the presence of some illegal
special characters like "<" ,
">" and "&" , you often face
the following error:
Error parsing XML,
line 1458, column
64: The reference
to entity "version"
must end with the
';' delimiter.
What are the special
characters in XML that
causes error?
XML is a human readable
form of textual data. It parses
all the text in a document
and gives errors for the
following 5 special
characters:
1. (<) - less than
2. (&) - ampersand
3. (>) - greater than
4. (") - double-quote
5. (') - apostrophe or single-
quote
The following three are more
crucial:
"<" will generate an error
because the parser
interprets it as the start
of a new element.
">" will generate an error
because the parser
interprets it as the end of
a start-tag or an end-tag
"&" will generate an error
because the parser
interprets it as the start
of a character entity.
Two ways to fix XML errors in
Blogger
XML errors can be avoided by
using two methods:
1. Use CDATA
2. Escape HTML entities
1. Use CDATA
The term CDATA refers to
(Unparsed) Character Data
which is used about text data
that should not be parsed by
the XML parser. To avoid
errors, all script code is
enclosed inside a CDATA
section. Everything inside a
CDATA section including the
5 special characters is
ignored by the parser.
A CDATA section starts with
" ":
Next time when you add your
Facebook code, enclose it
inside CDATA as shown
below:
All your script code will exists
inside the CDATA and blogger
editor will not parse the
script code and thus wont
give any errors.
The reason why Facebook
script gives errors in blogger
is due to the presence of a
special character ( &) that is
used before the variable
"version" as highlighted in
the code above. "&" will
generate an error because
the XML parser interprets it
as the start of a character
entity and thus it prompts an
error that says:
The reference to
entity " version"
must end with the
';' delimiter.
2. Escape HTML entities
Another simple method is to
escape all 5 special
characters and instead use
the legal characters as
alternatives to the above 5.
Replace < with <
Replace > with >
Replace " with "
Replace ' with '
Replace & with &
PS: Note how every
alternative character set
ends with a delimiter (;)
This method will help you
encode your AdSense code
and paste it inside your
template without errors. It
will also help you paste
HTML code inside blogger
comments !
This method is also called as
HTML encoding and we
have built a Special tool for
this purpose to help you
encode HTML characters with
ease.
