The \G anchor does no harm, but is not necessary in the OPed example case (/g modifier causes match position to be preserved in void/boolean/scalar context):

Win8 Strawberry 5.8.9.5 (32) Thu 12/17/2020 23:11:18
C:\@Work\Perl\monks
>perl -Mstrict -Mwarnings
my $string = " info

                    info


                100 - 2000


                  Kent";
my $word = "info";

$string =~ /$word\s*?(\S+)/g;
my $next_word = $1;     my $nwo = $-[1];  # offset of start of capture
$string =~ /\s*?(\S+)/g;
my $next_word_2 = $1;   my $nwo_2 = $-[1];

print "The next word after $word is $next_word @ $nwo \n";
print "The next word or number after $next_word is $next_word_2 @ $nwo
+_2 \n";
^Z
The next word after info is info @ 27
The next word or number after info is 100 @ 50
[download]

(Repeated words are also handled properly with/without \G.)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.